ISSUE-1007: trimming whitespace from accessible names and accessible descriptions
trimming whitespace from accessible names and accessible descriptions
- State:
- OPEN
- Product:
- SVG Accessibility API Mappings
- Raised by:
- Fred Esch
- Opened on:
- 2016-01-22
- Description:
- The accessible name and accessible description calculation skips trimming whitespace. Joanie Diggs points out in her email that Joseph will be updating the ARIA 1.1 spec to include whitespace trimming in name and description calculations (that was in ARIA 1.0 but omitted in error from ARIA 1.1).
This my reply email https://lists.w3.org/Archives/Public/public-svg-a11y/2016Jan/0032.html.
So the question is do we need to update any docs to reflect trimming of whitespace in the name and description calculations? I think it may be needed in an editors note...
- Related Actions Items:
- No related actions
- Related emails:
- SVG accessibility task force Agenda Tuesday 1 pm Eastern February 9, 2016 (from fesch@us.ibm.com on 2016-02-05)
- RE: Next meeting Feb 9, Issues raised by Joanie Diggs and Actions (from tink@tink.uk on 2016-01-29)
- Next meeting Feb 9, Issues raised by Joanie Diggs and Actions (from fesch@us.ibm.com on 2016-01-27)
- svg-a11y-ISSUE-1007: trimming whitespace from accessible names and accessible descriptions [SVG Accessibility API Mappings] (from sysbot+tracker@w3.org on 2016-01-22)
Related notes:
Joanie, also would like clarifying language on whitespace/capitalization when it applies to a accessible description calculation (and title).
Subject: Re: [aria] SVG-AAM: Issues with the use of title attribute in name and description calculation (#137)
Another one for you. The tests in the wiki include:
if given <circle id="test" aria-label="bob" cx='50' cy='100' r='15'><title>bob</title></circle> then accessible description = BLANK
But in the SVG AAM's Name and Description, the spec states:
Otherwise, if performing a text alternative computation for an accessible description, and the current node has at least one direct child title element, but the title elements were not used when generating the accessible name for the node, then select the appropriate title based on the language rules for the SVG specification, and return the title text content as the description.
Taking the spec as written and the test case above: The accessible name came from aria-label="bob" (Step 2C of the Core ACCName AAM); NOT from the title element. Thus according to the spec text quoted above, because there is at least one direct child title element which was not used when generating the accessible name, user agents should return the title text content as the description.
Either the test expectations are incorrect or the spec needs some clarifying language.
If you believe the test expectations are correct, the new clarifying language should probably take into account things like the strings being different, but only with respect to case and/or whitespace. (i.e. to what degree are user agents expected to judge "sameness" in author-provided strings?)
—
Reply to this email directly or view it on GitHub.
Display change log
