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
About a year I ago I privately forked tota11y to form the basis of my Dissertation project. A few months ago I was able to publicly release my project as a WebExtension for Mozilla Firefox and release the code under the same MIT license.
My project changed focus slightly from tota11y as I was focusing more on automated testing and the WC3's WCAG guidelines rather than visualisation. Although the user interfaces and intended use cases are different, I was able to keep the same Plugin interface from /plugins/base.js intact.
This means plugins from the two projects can be shared with very minor changes needed.
I have written plugins/tests for the following and if possible would like to contribute them back to tota11y:
WCAG 1.4.4 Resize Text & WCAG 1.4.12 Text Spacing specifications for recommended maximum changes from user style sheets that websites should support (ie text doesn't get clipped if enlarged 200%)
WCAG 2.5.3 Label in name guideline for programmatically determined text and visible labels matching to support speech input users
Table markup problems
WCAG 1.4.2 autoplaying audio guidelines
Extensions to the Labels plugin to test progress and meter elements.
Extensions to the Image alt-text plugin to test video elements for captions and audio descriptions (WCAG 1.2.2 and WCAG 1.2.5 respectively)
Extension for the Image alt-text plugin to test for alt text on input elements of type image
In my Dissertation project I have included references to the WCAG guidelines for all plugins and tests, and more supporting information in each about page. The text for the plugins in tota11y are a lot more terse right now.
For this process should I be condensing down the supporting information in the plugins/tests I have written and pull requesting each plugin/test to this project one by one?
One additional concern is that the addition of 4+ plugins fills up the toolbar by quite a lot. This has not been a problem for me because my WebExtension uses a sidebar and the plugins in the toolbar scroll, but might pose a problem on small screens for tota11y.
The text was updated successfully, but these errors were encountered:
Skeletonxf
changed the title
Additional plugins
Merging in additional plugins
May 25, 2019
Hi
Thanks for creating and releasing this project!
About a year I ago I privately forked tota11y to form the basis of my Dissertation project. A few months ago I was able to publicly release my project as a WebExtension for Mozilla Firefox and release the code under the same MIT license.
https://github.com/Skeletonxf/totally-automated-a11y-scanner
My project changed focus slightly from tota11y as I was focusing more on automated testing and the WC3's WCAG guidelines rather than visualisation. Although the user interfaces and intended use cases are different, I was able to keep the same
Plugin
interface from/plugins/base.js
intact.This means plugins from the two projects can be shared with very minor changes needed.
I have written plugins/tests for the following and if possible would like to contribute them back to tota11y:
WCAG 1.4.4 Resize Text & WCAG 1.4.12 Text Spacing specifications for recommended maximum changes from user style sheets that websites should support (ie text doesn't get clipped if enlarged 200%)
WCAG 2.5.3 Label in name guideline for programmatically determined text and visible labels matching to support speech input users
Table markup problems
WCAG 1.4.2 autoplaying audio guidelines
Extensions to the
Labels
plugin to testprogress
andmeter
elements.Extensions to the
Image alt-text
plugin to testvideo
elements for captions and audio descriptions (WCAG 1.2.2 and WCAG 1.2.5 respectively)Extension for the
Image alt-text
plugin to test for alt text on input elements of type imageIn my Dissertation project I have included references to the WCAG guidelines for all plugins and tests, and more supporting information in each about page. The text for the plugins in tota11y are a lot more terse right now.
For this process should I be condensing down the supporting information in the plugins/tests I have written and pull requesting each plugin/test to this project one by one?
One additional concern is that the addition of 4+ plugins fills up the toolbar by quite a lot. This has not been a problem for me because my WebExtension uses a sidebar and the plugins in the toolbar scroll, but might pose a problem on small screens for tota11y.
The text was updated successfully, but these errors were encountered: