Public document·View comments·Disposition of Comments·
Accessibility Guidelines Working Group Other specs in this tool Accessibility Guidelines Working Group's Issue tracker
1-20 21-30
Not all comments have been marked as replied to. The disposition of comments is not complete.
In the table below, red is in the WG decision column indicates that the Working Group didn't agree with the comment, green indicates that a it agreed with it, and yellow reflects an in-between situation.
In the "Commentor reply" column, red indicates the commenter objected to the WG resolution, green indicates approval, and yellow means the commenter didn't respond to the request for feedback.
Commentor | Comment | Working Group decision | Commentor reply |
---|---|---|---|
LC-2902 |
|
The proposed resolution is to merge the new example. It was already merged accidentally, but we can modify the example or pull it entirely. | tocheck |
LC-2898
Devarshi Pant <devarshipant@gmail.com> (archived comment) |
|
Thank you for your comment. The JAWS key referenced does apply to this technique. The keystroke does trigger JAWS to announce the page title but it also then announces the heading immediately above where the user is on the page. We use this keystroke rather than the JAWS Key + F6 keystroke because the JAWS heading list doesn't provide the context for the user to be able to determine what heading section the currently focused link is within. As a result, we will leave the technique as it currently reads. Thank you for your comment. |
yes |
LC-2882
Wilco Fiers <w.fiers@accessibility.nl> on behalf of Accessibility Foundation (archived comment) |
|
Thank you for your comment. Technique H69 does note that "...techniques assume that people needing special user agents (including AT or special plug-ins) will get and be using that ...". The user agent section also notes that most screen reader software support heading navigation. A free screen reader like NVDA can be operated with speech off and yet allow keyboard navigation to support sighted keyboard-only users. VoiceOver can be used likewise on Mac OSX. Technique H70 has been deprecated in the past, and is no longer included in the Techniques document. Therefore, the Working Group believes no changes are warranted at this time to techniques H69 or H70. |
yes |
LC-2881
Wilco Fiers <w.fiers@accessibility.nl> on behalf of Accessibility Foundation (archived comment) |
|
Thank you for the comment. You are correct in stating that 1.4.1 does not allow for information to be conveyed by color alone, and that is what this technique seeks to address. Using this technique, in addition to color being used to identify links from surrounding text the relative luminance difference of 3:1 or greater (paired with additional confirmation when the user tabs to or hovers over the links) allows the links to meet 1.4.1. To help make this more clear, we are adjusting the applicability sentence from: Colored text when color alone is used to convey information such as words that are links in a paragraph To: Text with links which lack decorative effects such as underlining that typically serve to help users identify links from surrounding text. We will leave this as a sufficient technique. |
tocheck |
LC-2872
Carlos A Velasco <carlos.velasco@fit.fraunhofer.de> (archived comment) |
|
Carlos, Thank you for your comment. We have moved the location of the source documents for WCAG techniques (as well as the understanding documents and the WCAG standard itself) to GitHub. This is the official repository. These source documents are updated as part of the process of updating the public HTML versions of these documents, and thus will be in sync with the technique document releases. It is worth noting that there will also need to be at least one development branch for these documents so the main branch can represent the current public stable version and the development branch can be modified leading up to an update. Regarding reporting issues via GitHub, people are welcome to submit issues or make modifications to the source documents on a local copy and submit pull requests. The working group will review issues and pull requests for non-editorial issues, but simple editorial pull requests may be accepted by the editors. |
yes |
LC-2897
EOWG <w3c-wai-eo@w3.org> (archived comment) |
|
Thank you for your comment on ARIA10 and F65. The working group has updated ARIA10 to restrict the use of ARIA10 to situations where the element does not allow the alt attribute. For F65, the working group has adjusted the language to allow for ARIA attributes to be used on image elements, but the test procedure explicitly calls out the need to verify that the attribute used is accessibility supported or else the failure will apply. In addition, F65 also indicates that use of the alt attribute is the preferred way of providing image accessibility to encourage its ongoing use. |
tocheck |
LC-2907
EOWG <w3c-wai-eo@w3.org> on behalf of Fraunhofer FIT |
|
Thanks for your comment. As we discussed, we are moving this issue to the tracking system for issues raised by Working Group members. [1] We will address this using that process. [1] https://www.w3.org/WAI/GL/track/issues/37 |
tocheck |
LC-2904
EOWG <w3c-wai-eo@w3.org> on behalf of Fraunhofer FIT |
|
Thanks for your comment. We have updated the test procedure to reflect the HTML spec correctly: For client-side image maps, check that the value of the usemap attribute is a URI that references a valid name or id. |
tocheck |
LC-2901
EOWG <w3c-wai-eo@w3.org> |
|
Accept pull request. Code change is viewable at https://github.com/w3c/wcag/pull/9/files | tocheck |
LC-2885
Wilco Fiers <w.fiers@accessibility.nl> on behalf of Accessibility Foundation (archived comment) |
|
Thank you for your comment. The Working Group agrees that this technique is applicable to all technologies and will be moved to a General Technique. This change will appear in the next public review draft. |
tocheck |
LC-2886
Wilco Fiers <w.fiers@accessibility.nl> on behalf of Accessibility Foundation (archived comment) |
|
Thank you for your comment. At this time the Working Group feels that this should remain a CSS technique. The Test Procedure has been updated with language specific to checking for scripting controls that allow the user to change the CSS. This change will appear in the next public review draft. |
tocheck |
LC-2887
Wilco Fiers <w.fiers@accessibility.nl> on behalf of Accessibility Foundation (archived comment) |
|
Thank you for the comment. We agree that this technique is very general and we will classify this as a general technique in the next update. | tocheck |
LC-2892
Devarshi Pant <devarshipant@gmail.com> (archived comment) |
|
Thanks for your comment. The Working Group agreed that the title of this failure technique is unclear, but on further reflection feels that the reason the title is not clear is because the failure technique is not clear. The key issue is that the phrase "at a location that users may bypass" is very difficult to interpret. Rather than a overly general failure technique, the working group will ensure that there are enough sufficient techniques that address this success criteria. We will remove this failure technique in the next update of the techniques. | tocheck |
LC-2873
Devarshi Pant <devarshipant@gmail.com> (archived comment) |
|
Thank you for the comment. We've made changes to address your comments. | tocheck |
LC-2874
Devarshi Pant <devarshipant@gmail.com> (archived comment) |
|
Thank you for the comment. We have modified the wording of the sentence in question (changed scope to "area") The user is logged into a secured area of a site, and following a link to a page outside of the secured area would terminate the user's logon. We have also corrected the grammatical error mentioned in part B of your comment. Thanks again for your comment! |
tocheck |
LC-2875
Devarshi Pant <devarshipant@gmail.com> (archived comment) |
|
Thanks for the comment. We've fixed this as you recommend. | tocheck |
LC-2899
Devarshi Pant <devarshipant@gmail.com> (archived comment) |
|
Thank for for the corrections, we've made changes to address your comments. | tocheck |
LC-2896
EOWG <w3c-wai-eo@w3.org> (archived comment) |
|
Thank you for the correction, we've made the change as you suggested. | yes |
LC-2894
Leona Zumbo <Leona.Zumbo@visionaustralia.org> on behalf of Vision Australia (archived comment) |
|
Thank you for your comment. The PDF examples are able to be updated continuously, and we have identified and repaired the issues you raised with the example files. The files are published and currently replace the files you identified as having errors. | tocheck |
LC-2883
Tom Siechert <tsiechert@csufresno.edu> on behalf of California State University Fresno (archived comment) |
|
Thank you for the comment. The technique H93 that you are referencing is from an early draft of WCAG 2.0 dating back to 2005. This technique was removed in 2006 and the H93 code was repurposed in the 2010 techniques update. We are sorry if this caused confusion, we do try to avoid re-using technique codes but since the first use was prior to WCAG 2.0 reaching Recommendation status this was not a concern in 2010 when the current version of H93 was added. We are also looking into modifying the page template for techniques to include a link to the most current version of each technique. Until this link is established, to ensure that you are reviewing the latest version of the techniques please visit the current techniques document at http://www.w3.org/TR/WCAG20-TECHS/. | tocheck |
1-20 21-30