Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Writer: Spelling errors not exposed semantically via accessibility APIs | ||
---|---|---|---|
Product: | General | Reporter: | James Teh <jamie> |
Component: | accessibility | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Minor | ||
Priority: | P3 | CC: | issues, steve.yin.aoo |
Version: | 4.1.0-dev | Keywords: | accessibility |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | |||
Issue Blocks: | 121767 |
Description
James Teh
2014-03-06 03:03:45 UTC
Confirmed. In Symphony, I used UNDERLINE_WAVE (CharUnderline 10) & 0x00FF0000 (CharUnderlineColor) to mark spelling errors. This is not a good way to expose the information to the ATs. I will modify it to use the standard way. Thanks. (In reply to James Teh from comment #0) > Str: > 1. Open a new document in Writer. > 2. Ensure Writer is set up to do spell checking for English. > 3. Type "My tset" (intentional typo, without quotes) and press space. > 4. Obtain the accessible for the paragraph just entered. > 5. Retrieve the text attributes for offset 3. > Expected: There should be an "invalid" attribute with a value of "spelling" > ("invalid:spelling"). > Actual: There is no "invalid" attribute. You can determine that there is a > spelling error because the CharUnderline attribute has a value of 10 (the > WAVE underline type). > > This isn't a major issue because ATs *can* determine that there is a > spelling error. However, this is obscure at best. Ideally, this should be > exposed semantically, rather than relying on the way it is displayed. |