pull down to refresh
0 sats \ 0 replies \ @jsonbits 19 Apr \ on: in case you haven't read Harrison Bergeron by Kurt Vonnegut BooksAndArticles
My boss at AT&T Labs actually read this to us on our first meeting in the office as new hires. We were founding the Corporate Accessibility Technology Office and trying to make our products accessible to people with disabilities. Great cautionary tale!
I would add that providing text labels will also help screen reader and voice dictation users identify and navigate the interface.
When providing text labels adjacent to forms and controls, they should also be programmatically defined as the primary accessible name for these controls and any adjacent image icons should be hidden from being announced by screen readers (usually through the use of
alt="" or aria-hidden).For voice dictation users, that accessible name should also match or at least include the visual text present on screen so that when voicing commands like "click update form", the software recognizes exactly which control they are attempting to activate.
The accessible name should contain the visible text, but not re-order it. For example:
Visible label = "Fizz Fuzz" Accessible name = 'Fizz Fuzz", "Fizz Fuzz Bang", or "Bang Fizz Fuzz", but not "Fizz Bang Fuzz", or "Bang Fuzz Fizz"
Interesting tool I saw demoed at CSUN AT Conference last week. Physical cards that represent JavaScript components which are arranged to iterate on the interaction design for specific features.
Have you looked into Stakwork.com?
Same here. One of my past colleagues getting told to sell their house for a loss and move to another city (where they will likely be laid off in the next round of cuts). They applied for 3 positions at my fiat job 2 they were qualified for and one they were overqualified for. Put in the time to write a nice cover letter, sent my recommendations to HR only to wait 4 weeks to be told they do not have anything to offer this person with 20 years experience in HW and Software engineering.
@Design_r Sorry it took me a bit to get around to this. Created a GH Issue here with a recommended usage table for color contrast accessibility of existing brand colors: https://github.com/stackernews/stacker.news/issues/1922
Feel free to comment or ask questions on the issue directly. Hoping to open the conversation on what voluntary standards or guidelines we can use to make the content more readable and usable for all.
Everyone should file for am extension tomorrow as a signal of intent. When we see all the people who intend to not file apply for an extension, then we will know what our numbers really are.
Beautiful post! As someone who is starting to dip their toes into open source contributions it can be a bit daunting, but also exhilarating to work on something you love. Trying to find the time outside of work has been difficult, but small consistent steps appear to be the key. Thanks for sharing your journey and encouraging others like myself.
We should do an accessibility review on a few of the color combinations in light mode and in some of the banner images with text, but for the most part everything has really good contrast in the default dark mode. Very nice to have the design guide as a tool to keep everything consistent. Love the icons. Great work!