You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- criterion: "Section 1194.24 Video and Multi-media Products"
21
21
support: Supports with exceptions
22
-
comments: "Training materials available via [youtube.com/github](https://www.youtube.com/user/github) and [youtube.com/githubguides](https://www.youtube.com/user/githubguides)"
- criterion: "(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually."
40
40
support: Supports with exceptions
41
-
comments:
41
+
comments:The items inside of Assignees and Clear Assignees require a user to tab to the submenu items versus use down/up arrows.<br /><br />Labels option does not follow typical keyboard actions.
42
42
- criterion: "(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer."
43
43
support: Supports
44
44
comments: GitHub desktop applications are built using platform-specific standards and best practices where possible.
45
45
- criterion: "(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes."
46
46
support: Supports with exceptions
47
-
comments:
47
+
comments:The Filter control on the web client does not receive keyboard focus.<br /><br />When changing color value on Labels button, focus unexpectedly moves to top of page.<br /><br />When activating certain controls such as “delete” button for labels and links from buttons, expanded filters or filtered search results, focus does not move to the new dialog.<br /><br />When creating a “new issue,” focus does not move automatically to the title field.<br /><br />Focus order when creating a “new issue” is not logical.<br /><br />Focus does not go to user name/repo name, when activating "Skip to Main" button.<br /><br />In GitHub Notifications page, notifications are read out of logical order.<br /><br />When activating the branch dropdown menu, focus is not visible on “Skip to Content” link.
48
48
- criterion: "(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text."
49
49
support: Supports with exceptions
50
-
comments:
50
+
comments: When making an edit to the markdown of the GitHub ReadMe file, the field is not announced as editable and “no new line at end of file” icon is not announced by screen reader.<br /><br />Across a number of areas in the GitHub Marketplace, selected elements are not announced as selected and decorative elements are not skipped by screen readers.<br /><br />Throughout the site, links are only described as links without additional context. For example, in GitHub repositories, new links are described only as new link without additional context. Social media links (e.g., GitHub Twitter link) are only described as “link.”<br /><br />Assignees button, and type or choose name control do not have the correct accessible control name.<br /><br />No additional announcements are made after making a pull request although there are visual displays of errors and other information.<br /><br />When reviewing search results data, checkboxes for labels and select all issues checkboxes do not have accessible names.<br /><br />On GitHub Help page, search button does not have the control type described.<br /><br />On GitHub Repo Settings Collaborators, the dismiss message button is announced before message is read and “Delete this repository” dialog sets focus to input field and ignores accompanying text.<br /><br />When not signed in, button names are not read (such as Watch or Fork) and instead, you must be signed in is read when landing on the control.
51
51
- criterion: "(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance."
52
52
support: Supports
53
53
comments: "All iconography are rendered via the [Octicons](https://octicons.github.com/) library."
@@ -68,10 +68,12 @@ data:
68
68
comments:
69
69
- criterion: "(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz."
70
70
support: Supports
71
-
comments: Applications have no flashing or blinking elements
71
+
comments: Applications have no flashing or blinking elements.
72
72
- criterion: "(l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues."
73
73
support: Supports with exceptions
74
-
comments:
74
+
comments: When making an edit to the markdown of the GitHub ReadMe file, the field is not announced as editable.<br /><br />No additional announcements are made after making a pull request although there are visual displays of errors and other information.<br /><br />Assignees button and “Type or choose a name edit field” have accessible names that do not match the visual control names.<br /><br />Input errors on GitHub.com sign up page are not announced.
75
+
76
+
75
77
76
78
"Section 1194.22 Web-based Intranet and Internet Information and Applications":
77
79
product: GitHub.com and GitHub Enterprise
@@ -96,7 +98,7 @@ data:
96
98
comments: No client-side image maps are used.
97
99
- criterion: "(g) Row and column headers shall be identified for data tables."
98
100
support: Supports with exceptions
99
-
comments:
101
+
comments:GitHub Enterprise dashboard has a table that is not identified as a data table.
100
102
- criterion: "(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers."
101
103
support: Not applicable
102
104
comments:
@@ -120,10 +122,10 @@ data:
120
122
comments:
121
123
- criterion: "(o) A method shall be provided that permits users to skip repetitive navigation links."
122
124
support: Supports with exceptions
123
-
comments:
125
+
comments:On GitHub Enterprise, the user must tab through repetitive links.
124
126
- criterion: "(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required."
125
127
support: Not applicable
126
-
comments: No timed responses are required.
128
+
comments: Timed responses are not required.
127
129
128
130
"Section 1194.23 Telecommunications Products":
129
131
product:
@@ -185,7 +187,7 @@ data:
185
187
comments: "Training materials available at [youtube.com/github](https://www.youtube.com/user/github) and [youtube.com/githubguides](https://www.youtube.com/user/githubguides). All GitHub videos are fully closed captioned. <br /><br />For more information on YouTube's accessibility see [support.google.com/youtube/answer/189278](https://support.google.com/youtube/answer/189278?hl=en)"
186
188
- criterion: "(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described."
187
189
support: Supports with exceptions
188
-
comments:
190
+
comments:Training videos posted via YouTube video player do not include audio description.
189
191
- criterion: "(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent."
190
192
support: Supports
191
193
comments: Viewers may toggle closed captioning using YouTube's native closed-captioning functionality.
@@ -254,22 +256,22 @@ data:
254
256
criteria:
255
257
- criterion: "(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided."
256
258
support: Supports with exceptions
257
-
comments: All Git-based file operations can be performed via the text-only Git command line interface using assistive technology, and all account management and social interactions (e.g., commenting on an issue) can be performed via GitHub.com or GitHub enterprise with assistive technology.
259
+
comments: Account management and social interaction scenarios have focus order, name, role, value, accessible name, and info and relationship issues that may prevent some scenarios from being completed.
258
260
- criterion: "(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided."
259
261
support: Supports with exceptions
260
-
comments: All GitHub product support the use of assistive technology and provide the ability, through the user's web browser or operating system to increase the font size.
262
+
comments: Zooming to certain levels will cause info on the screen to be pushed off and require horizontal scrolling.<br /><br />There is insufficient color contrast on a number of links, dialogs and controls.
261
263
- criterion: "(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided"
262
264
support: Supports
263
-
comments: Products do not use auditory feedback.
265
+
comments: Products do not require auditory feedback.
264
266
- criterion: "(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided."
265
267
support: Not Applicable
266
268
comments: Products do not use auditory feedback.
267
269
- criterion: "(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided."
268
270
support: Supports
269
-
comments: Products do not support speech input.
271
+
comments: Products do not require speech input.
270
272
- criterion: "(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided."
271
273
support: Supports with exceptions
272
-
comments: No interactions require simultaneous user actions or depend solely on fine motor controls.
274
+
comments: Submenus and other control areas may require using irregular keyboard actions such as tabbling versus up/down arrows and focus order for creating and managing issues in GitHub is illogical.
273
275
274
276
"Section 1194.41 Information, Documentation and Support":
0 commit comments