Coder Social home page Coder Social logo

Comments (2)

aoelen avatar aoelen commented on June 4, 2024

While working on the accessibility issues there are some points I want to address.

1. Semantic UI framework
This framework is from an accessibility perspective a bad choice. Especially for forms, it requires a lot of work to make them accessible. Right now, I have manually added some CSS classes but in the long term it is not desirable if a lot of custom CSS has to be added. Additionally Semantic UI is currently not actively maintained anymore. Currently Bootstrap is doing a better job with respect to accessibility. I think it makes sense for a gradual transition to Bootstrap.

2. Complicated forms
Some forms on the platform are complicated. For example, the add deck page (https://slidewiki.org/addDeck) contains a lot of form fields that are not required. I think it makes sense to have a good look at all forms on the platform, and try to find out if some form fields can be grouped into a hidden container. Then a button with "Show advanced options", can make the hidden form items appear. I think this lowers the barriers when creating a new deck.

3. Collect accessibility requirements in a wiki
I think it would be a good idea to create a wiki page that lists all the accessibility guidelines of SlideWiki. I've created an example at: https://github.com/slidewiki/slidewiki-platform/wiki/Accessibility-guidelines-SlideWiki This makes it easier for developers to make their components accessible. This also provides some guidance on how certain components should be implemented and is helpful when referring to a certain rule. Maybe in the future some linter rules can be added based on this document. @VivienDZB you think this makes sense?

@bwulff @kadevgraaf any thoughts on this?

from slidewiki-platform.

VivienDZB avatar VivienDZB commented on June 4, 2024

@aoelen Actually those accessibility guidelines already exit on the WCAG page...also with examples on how to make web pages accessible. But of course they are very extensive and mostly kept relatively general. So I think it would make sense to create this wiki page and collect the guidelines that are specific to SlideWiki and add examples that give further information on how to solve those issues.

from slidewiki-platform.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.