Hi Claudia, One of the core features of recent versions of Angular (2 and above) is ARIA-enabled components: https://angular.io/features So, a base level of accessibility is "built-in" to some extent, but I'm certain it can be improved upon in our UI code.
During the decision making process on Angular, we had help from the U of Kansas on performing some basic accessibility tests against the Angular platform to ensure it would meet our needs. The tests came back positive, with only minor issues (from our own code) at the time. See this old ticket, which describes the testing process that was performed against the prototype last year: https://github.com/DSpace-Labs/angular2-ui-prototype/issues/113 Currently, as you've seen, development has moved over to the dspace-angular project: https://github.com/DSpace/dspace-angular/ The base platform is the same, but we haven't (yet) done a repeat of the accessibility tests from last year. I fully agree that this is a great opportunity to ensure DSpace has a highly accessible, modern UI. As we are still quite early in the DSpace 7 UI development process, we have not done any additional formalized testing of the UI for accessibility. However, prior to the DSpace 7 final release, I'd like to see more formal accessibility testing occur (and if there is anyone interested in helping us in this way, please do get in touch). In the meantime, there is the opportunity for interested folks (or a team of folks) to begin doing some basic accessibility testing against our demo site: https://dspace7-demo.atmire.com/ . This demo site is always running the latest version of the DSpace 7 UI (as it auto-updates on any code changes). Any accessibility issues found should be logged as bugs in our GitHub issue tracker for the project: https://github.com/DSpace/dspace-angular/issues (that way we can assign them to DSpace 7 developers to be fixed ASAP) I like your idea of establishing more formal guidelines for DSpace accessibility (and the Angular UI specifically perhaps). I'd welcome someone (or multiple someones) to consider drafting some accessibility notes on our Wiki. This could start with some simple guidelines/goals, and perhaps even include tools for testing, basic best practices, etc. If there is such interest, we could even consider forming an Accessibility Working Group (or similar) to discuss how to generate these guidelines or provide feedback from their own experiences. In any case, this is definitely a place we could use help! I cannot claim anyone on the DSpace 7 UI team is an accessibility expert, but we'd all like to ensure the new UI is meeting the accessibility goals of our user community. So, help in defining/formalizing those goals and providing bug reports on existing issues would be appreciated. - Tim On Wed, Nov 29, 2017 at 5:55 AM Claudia Jürgen < [email protected]> wrote: > Hi all, > > as I have been once again asked off list about accessibilty and DSpace I > thought to raise the issue. > This has been an ongoing feature request with DSpace since the beginning. > There are a couple of tickets with regards to it. > Two UI's and a lot of changes made it difficult and costly to address the > issue for DSpace in general. > > I wonder whether the fresh start with Angular will provide the opportunity > to do it now. > It was one argument during the prototyping challenge but I did not find > anything at > https://wiki.duraspace.org/display/DSPACE/DSpace+7+-+Angular+UI+Development > Being completly new to Angular, just installed dspace angular once to have > a peek and looked a a tutorial. > There are a couple of tutorials and the old angular js did have an aria > module, but I did not find anything similar in the newer versions. > > But actually it would first require to define which level and standards or > even best practices of accessibility we want to support/adpopt in the long > run in DSpace and create guidelines. > What are your thoughts? > > cu > > Claudia > > > -- > Claudia Juergen > Eldorado > > Technische Universität Dortmund > UniversitätsbibliothekVogelpothsweg 76 > 44227 Dortmund > <https://maps.google.com/?q=Vogelpothsweg+76%0D+44227+Dortmund&entry=gmail&source=g> > > Tel.: +49 231-755 40 43 <+49%20231%207554043> > Fax: +49 231-755 40 32 > <+49%20231%207554032>[email protected] > > > > > *Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie > ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für > diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender > und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz > per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, > wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder > durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. > Important note: The information included in this e-mail is confidential. It > is solely intended for the recipient. If you are not the intended recipient > of this e-mail please contact the sender and delete this message. Thank > you. Without prejudice of e-mail correspondence, our statements are only > legally binding when they are made in the conventional written form (with > personal signature) or when such documents are sent by fax. * > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
