Hi Folks, My university is about to launch a summer program with courses focused on the pandemic. The primary marketing/explanation materials are built in TiddlyWiki. The soon-to-be-announced link is here: https://pvfiles.sunypoly.edu/pandemic-studies.html
Our web architect identified a few issues to be resolved "in order to meet the WCAG 2.0 success criteria," and I was wondering if anyone has encountered these issues, or has any idea what is being discussed? Here is what I've received: Outlined below are the remaining errors being thrown by the WAVE tool. You > can use the WAVE Chrome extension > <https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh?hl=en-US> > to > replicate these errors. > > *1. Document language tag*More information - > https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html > Please implement a "lang" attribute within the <html> tag. The following > line will be sufficient: > <html lang="en"> > > *2. Empty buttons*The button tags wrapped around the SVGs for the mobile > menu hamburger icons don't contain any text descriptions indicating the > function of the button. This can be resolved by adding an "aria-label" > attribute to the button tags. The two instances being flagged are > > - nav.tc-menubar -> .tc-menubar-*wide* -> .tc-menubar-list -> > .tc-menubar-narrow -> <*button class>* > > > - nav.tc-menubar -> .tc-menubar-*narrow*-> .tc-menubar-list -> > .tc-menubar-narrow -> <*button class> * > > > *3. Form labels*Form inputs must be properly labelled. This can be > accomplished by wrapping the form labels in a <label> tag with a "for" > attribute referencing the ID of the input element (Ex: <label > for="select-test">This is a label</label><select id="select-test">...). > This also entails that an ID attribute can be added to the control/input > element. However, the label tag and its for attribute, as well as the ID > attribute for the select tiddler, are not rendered when the tiddler is > saved. The PickArtifactFirst and PickPerspectiveFirst tiddlers are example > instances where this error is being thrown. > An alternative method is to enable the "aria-label" attribute for the > select elements. > Note: In Tiddlywiki, the solution was to add a title attribute to form > control/input elements. We would like to avoid doing this if possible, as > it is not recommended by the W3C - > https://www.w3.org/WAI/tutorials/forms/labels/#using-the-title-attribute. Any help, much appreciated! And, of course, any thoughts or suggestions on the implementation of this wiki for this app would be welcome. It's pretty basic, making use of xlsx import tool and a bunch of templates. Last step in next day is to write a link to a pre-filled google form or wordpress form as the output. Thanks! //steve. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/979d069a-0bb8-42c2-a03f-72db71d93344%40googlegroups.com.
