Web accessibility/WACC301/Accessibility

Though we attempt to make all elements of the course conform with international accessibility guidelines, we must acknowledge a few accessibility issues that are out of our control or are done on purpose to demonstrate barriers.


 * Some external resources may not conform with accessibility guidelines.
 * Though possible to navigate the JSFiddle code samples embedded in the book, JSFiddle itself is a complex interface that can be difficult to navigate with a screen reader. Working in JSFiddle is not a requirement for the course but has been provided as a place to experiment with the code samples provided.
 * The rendered JSFiddle embedded examples found under the result tab are intentionally made inaccessible.
 * Prior to each embedded JSFiddle is a hidden bypass link to skip over the fiddle iframe.
 * The JSFiddle interface will extend beyond the width of a mobile screen and, thus, require scrolling.
 * Throughout the widget descriptions in chapters 4 to 6, we present code examples embedded from PasteBin. Though the code itself is readable with a screen reader, the highlighted solutions they contain are not distinguishable from other code in these samples when listening with a screen reader. Where possible, we have described the changes in the text preceding these code samples.
 * The GitHub website, which contains the book files used with activities in the course and is relatively accessible, can be difficult to navigate and use with a screen reader.
 * Third-party video content may not be captioned or may be captioned poorly.