rblades / dhworkbook_master Goto Github PK

Should we keep the tota11y button on the website to hold ourselves accountable to users? Not only can we quickly review any changes for accessibility, but users can keep us in check by having the tool readily available.

It could open up discussion on features and web accessibility, too, because not every 'error' is best changed. Some errors and warnings, if changed to the prescribed, could make the site less accessible.

Option to change text on entire site to OpenDyslexia font

We want instructions to be clear and the website accessible to all. But, what are the limits when it comes to the importance of failure and working through mistakes made in pedagogy. We are not writing an emergency aircraft manual where failure is not an option. We don't want to necessarily build in failure or make things difficult, but the appearance of such failures and annotations/discussion thereof are important in teaching this material and DH philosophy generally to students.

Home link is redundant with title link above, as well as Docs breadcrumb link in upper left corner. Must make sure that the title link defines with ARIA or 'role' it's function.

Bold text is more accessible than italicized. I've been changing an italicized text to bold.

We actively use Hypothesis to annotate the site to add a layer of interaction and discussion. However, we are thus partly responsible for any accessibility issues that come with Hypothesis, notably the contrast of the highlighted text with the site text/background.

We may need to use hypothesis for page notes instead of annotations, or adjust the site to contrast accessibly with Hypothesis.

Or, and I think this the best option, open a ticket with Hypothesis to expand the tool's accessibility around the web.

At the beginning of each page or section, add a word count and read time (perhaps there is a function for this in jinja?)

Screen reader goes through entire navigation on each new page. Need a way to skip the navigation. Propose adding a link to skip the navigation.

See this article on the subject

• Make sure internet explorer accessible
• Use Lynx browser to run through website
• Make sure text is resizable, yet still functional on mobile

Screen reader goes through entire navigation on each new page. Need a way to skip the navigation. Propose adding a link to skip the navigation.

See this article on the subject

Especially in links and instructions, must edit language to reflect accessibility - ex. 'visit' instead of 'see'; 'explore' instead of 'view'.

Designing for accessibility is hard and I see how it's easy to get stuck in the mindset of 'feature creep' (aka adding a new feature for every issue one may come across). The problem - which I will illustrate with the example of dyslexia - is that one might create more problems than they solve. For instance, if we added a user option to change the font style to OpenDyslexic font, it would require some javascript or jquery to flick the switch. A lot of people, however, disable javascript on their machines because it interferes with accessibility. Therefore, we may have provided a nice option, but alienated people who don't use javascript, use text browsers, etc.

And I think the solution is revealing itself. If the font is designed in relative sizing, text well spaced, using a sans serif, links easy to understand, content written appropriate, and alts set out properly, we've done the best we can and allow more people to access the content. Furthermore, we keep the design accessible and functional for whatever third party programs users may employ to match their accessibility needs.