[NFBCS] CSS

[Michael Ausbun]

Haoran,
I’m thrilled you are enjoying your braille classes at the LCB; your braille teacher is pretty cool, if I don’t say so myself—not that I’m bias or anything!
Automated testing
I will certainly take a look at the first two suggestions and your attached document. Regarding automated accessibility testing—such as in Microsoft’s insights and WAVE from webaim—everyone has their tools of preference. I actually prefer a combination of the ARC toolkit from the Paciello group, continuum explorer from level access, AXE from DeQue, and Siteimprove’s extension.
Remember that full automation only detects approximately 1/3 of the WCAG success criteria, with a variance of 33% for false positives and 35%  for false negatives. I prefer the arc toolkit as my primary because it fits right into the developer tools and thus I can interact with the DOM as I’m testing.
CSS:
Although certain parameters have been set by WCAG, I’m not certain  that the automated testing tools for accessibility will produce ideal user experiences a majority of the time as the rules are specifically set for pass/fail of the WCAG success criteria. It’s very likely other validation tools might speak to this more, with an emphasis on the specification draft by the W3C; I’m not certain though, as I haven’t researched much into validation tools!
In general:
I really appreciate your resource and your suggestion in checking out the validation tools; at the very least, ensuring no parsing errors are present would be nifty. If you find any other tips and tricks for writing good, clean, accessible CSS let me know!
Best,
Michael

--
Michael Duane Ausbun, MA
Accessibility Specialist, Program Development,
Universal Design and Accessibility Team
Salt Lake City, Utah
[WGU Learning Experience]

Western Governors University
4001 South 700 East, Suite 700
Salt Lake City, UT 84107
Michael.ausbun at wgu.edu


[Western Governors University]<wgu.edu>



From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Haoran Wen via NFBCS
Sent: Sunday, December 15, 2019 9:18 PM
To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org>
Cc: Haoran Wen <manhouyin at gmail.com>
Subject: Re: [NFBCS] CSS

[EXTERNAL EMAIL] WARNING: Be wise. Be cautious.

Hi Michael!

I spent the past summer as a research intern trying to solve this problem.
There are a good amount of CSS validators out there that can be used to
validate the CSS and websites that was written against specified rules.
I suggest looking into:
1. https://jigsaw.w3.org/css-validator/<https://jigsaw.w3.org/css-validator/>
2. elad2412/css-accessibility-validator: CSS Accessibility Validator for
your HTML <https://github.com/elad2412/css-accessibility-validator<https://github.com/elad2412/css-accessibility-validator>>
3. https://wave.webaim.org<https://wave.webaim.org>
4. https://accessibilityinsights.io/docs/en/web/overview<https://accessibilityinsights.io/docs/en/web/overview>
I have also attached a document containing a complete list of the
compilation of CSS validator I have found from my research.

I hope this helps,
Haoran

P.S. Braille class with Bre has been great.



On Sun, Dec 15, 2019 at 8:31 PM Michael Ausbun via NFBCS <nfbcs at nfbnet.org<mailto:nfbcs at nfbnet.org>>
wrote:

> Greetings,
> I'm curious what non-visual techniques folks use when working within CSS.
> Is determining the CSS' final output/user experience largely dependent on a
> reader/sighted person? Are there generally accepted best practices for CSS;
> such as ensuring all elements have a particular margin/padding/etc?
> Trying to figure out the most efficient way to produce visually-appealing
> or inclusive design when using CSS. Writing CSS is no problem; just not
> sure about the checking, without using a reader.
> Much appreciated!
> Respectfully,
> Michael
>
> _______________________________________________
> NFBCS mailing list
> NFBCS at nfbnet.org<mailto:NFBCS at nfbnet.org>
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org<http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org>
> To unsubscribe, change your list options or get your account info for
> NFBCS:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/manhouyin@gmail.com<http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/manhouyin@gmail.com>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14468 bytes
Desc: image001.png
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20191216/5865caa6/attachment.png>