@@ -25,7 +25,7 @@ with regard to the WCAG 3.0 standard.
25
25
26
26
Specifically, it outlines where Open OnDemand does not meet this standard.
27
27
It may also link to a ticket that developers track. You can search
28
- [ all accessability issues] ( https://github.com/OSC/ondemand/issues?q=is%3Aissue+is%3Aopen+label%3Aarea%2Faccessibility )
28
+ [ all accessibility issues] ( https://github.com/OSC/ondemand/issues?q=is%3Aissue+is%3Aopen+label%3Aarea%2Faccessibility )
29
29
as well.
30
30
31
31
## 3rd Party Apps
@@ -40,7 +40,7 @@ are not documented here.
40
40
## Accessibility by URL
41
41
42
42
Each section below documents a single webpage. If the section heading
43
- includes sub URLs this means the same webpage is used to genereate content
43
+ includes sub URLs this means the same webpage is used to generate content
44
44
based on the URL.
45
45
46
46
As an example in the section entitled ` /pun/sys/dashboard/files and sub URLs ` ,
@@ -52,9 +52,9 @@ as `/pun/sys/files/fs/home/jessie`.
52
52
These issues affect all or most URLs.
53
53
54
54
- Most URLs have the main navigation bar. This is a list of issues with that navigation
55
- bar. See this issue for [ navigation bar accessability issue] ( https://github.com/OSC/ondemand/issues/945 )
55
+ bar. See this issue for [ navigation bar accessibility issue] ( https://github.com/OSC/ondemand/issues/945 )
56
56
for more details.
57
- - Screen readers will see the navigation bar landark as 'banner landmark', 'navigation'
57
+ - Screen readers will see the navigation bar landmark as 'banner landmark', 'navigation'
58
58
and 'navigation landmark', where really we should only have 1 single landmark.
59
59
- Many [ alerts don't notify screen readers.] ( https://github.com/OSC/ondemand/issues/2077 )
60
60
As an example, when you start an interactive session there's an alert to notify the user
@@ -66,8 +66,8 @@ This is the landing page and what the root URL `/` redirects to.
66
66
67
67
The landing page allows for site administrators to create panels. The panels we
68
68
distribute are covered in this document. Panels specifically created at any
69
- given site are unknown to us (the developers), have not and will not be assesed
70
- for accessability .
69
+ given site are unknown to us (the developers), have not and will not be assessed
70
+ for accessibility .
71
71
72
72
- [ The welcome logo does not provide alt text.] ( https://github.com/OSC/ondemand/issues/2067 )
73
73
- [ Message of the Day and pinned apps use heading levels 3 & 4 instead of 2 & 3.] ( https://github.com/OSC/ondemand/issues/2074 ) .
@@ -80,7 +80,7 @@ for accessability.
80
80
There are several issues with batch connect session cards.
81
81
- First when they change state, say from 'Queued' to 'Running' there's no notification that this happened.
82
82
- Secondly, there's no good organization of these cards. They should probably be in a list.
83
- - Lastly some of the text is off, like the session id link that is a UUID. It's an ambigous link.
83
+ - Lastly some of the text is off, like the session id link that is a UUID. It's an ambiguous link.
84
84
85
85
#### Batch connect app web forms
86
86
@@ -95,8 +95,8 @@ may have included.
95
95
- [ Dynamic form updates do not update the user.] ( https://github.com/OSC/ondemand/issues/2075 ) When a
96
96
user updates a form field, another form field may automatically be updated. There is no screen reader
97
97
notification when this occurs.
98
- - [ Resolution fields don't have the right labels.] ( https://github.com/OSC/ondemand/issues/2076 ) Resulution
99
- form fields have labels visible to sigted users, but screen-reader navigation does not automatically read
98
+ - [ Resolution fields don't have the right labels.] ( https://github.com/OSC/ondemand/issues/2076 ) Resolution
99
+ form fields have labels visible to sighted users, but screen-reader navigation does not automatically read
100
100
them. The user is forced to navigate around the form element to hear the label.
101
101
102
102
### /pun/sys/dashboard/noVNC-1.1.0/vnc.html
@@ -115,7 +115,7 @@ where we come to this conclusion.
115
115
- [ The files table does not notify users of updates] ( https://github.com/OSC/ondemand/issues/2080 ) .
116
116
When a user clicks through to another directory in the file browser table the table updates
117
117
with the contents of the chosen directory. However, screen-readers are not notified that this
118
- change has occured .
118
+ change has occurred .
119
119
- [ Screen-Readers read the sorting arrows in the files table] ( https://github.com/OSC/ondemand/issues/2081 )
120
120
when they should only read the column name.
121
121
- [ File browsing landmarks could be better.] ( https://github.com/OSC/ondemand/issues/2079 ) There's
@@ -125,12 +125,12 @@ where we come to this conclusion.
125
125
126
126
The shell application is considered completely inaccessible. Screen
127
127
readers do work on it a little, but it's so little as to be rendered
128
- completey useless.
128
+ completely useless.
129
129
130
130
The underlying library ` hterm ` does have support for accessibility but
131
131
we need some mechanism to turn it on.
132
132
133
- We have this ticket concerning [ shell accessability ] ( https://github.com/OSC/ondemand/issues/672 )
133
+ We have this ticket concerning [ shell accessibility ] ( https://github.com/OSC/ondemand/issues/672 )
134
134
to tracks this.
135
135
136
136
### /pun/sys/myjobs and sub URLs
0 commit comments