[NFBCS] CSS

[Haoran Wen]

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/
2. elad2412/css-accessibility-validator: CSS Accessibility Validator for
your HTML <https://github.com/elad2412/css-accessibility-validator>
3. https://wave.webaim.org
4. 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>
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
> 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%40gmail.com
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CSS validator table.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 101210 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20191215/83542af5/attachment.docx>