Striking the balance between accessibility and trendy design is the hard part.
For example, the green DN's "post a job" button in the right column. Looks nice, but the green background isn't 508 compliant with the white font. The green that is 508 compliant is an ugly forest green color. Its even worse, when the client's own brand colors are not even 508.
True but it also depends upon your target audience. For example, if we are targeting teens where color blind children of % are like 5 then you can go with it.
Really great article and some valuable insights. If you take topic requests, I'd love to see more about what website creation PLATFORMS could do to create better drag and drop platforms that support accessibility, and produce accessible websites.
This is a well written article and a good resource for those just starting out with a11y. Bit disappointed that it didn't deal with actually designing for a11y, which is hugely important. This involves not just technical stuff here but the IA, content, page structure, overall document semantics, hidden text to fill in gaps where visual cues are used, etc.
This is something that needs to be done as early in the design process as possible and tested with users and iterated upon before production even starts. Without it, a11y just becomes a box-ticking exercise—you'll never know if your product is truly accessible.