Skip to content
GitLab

Home · Changes

Page history
Update home authored by Michael Pluke's avatar Michael Pluke
Hide whitespace changes
Inline Side-by-side
home.md
View page @ 5d519d7e
# Background
EN 301 549 is the European standard on Accessibility requirements for ICT products and services. The latest published version, 3.2.1, can be downloaded [here](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf "EN 301 549").
It was originally written as a standard to be used in the context of ICT procurement, but it was updated to also allow it to be used means of showing conforming to the essential requirements of European Directive 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies. It is expected that EN 301 549 will be further updated to allow it to be used in other contexts and to ensure that it is based on the latest best practice. To ensure coherence of the updated EN 301 549, all changes must be done in a way that is consistent [with the design principles that apply to the document](https://labs.etsi.org/rep/HF/en301549/-/wikis/EN-301-549-Design-Principles).
It was originally written as a standard to be used in the context of ICT procurement, but it was updated to also allow it to be used means of showing conforming to the essential requirements of European Directive 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies. It is expected that EN 301 549 will be further updated to allow it to be used in other contexts and to ensure that it is based on the latest best practice. To ensure coherence of the updated EN 301 549, all changes must be done in a way that is consistent with [the design principles that apply to the document](https://labs.etsi.org/rep/HF/en301549/-/wikis/EN-301-549-Design-Principles).
# The purpose of this site
This site has been created to help to enhance and broaden participation in deciding on what future updates should be made (although final decisions on what is and what is not implemented will continue to rest with a CEN/CENELEC/ETSI Joint Working Group (JWG) on “eAccessibility”).
# How the site is organised
## Issues
Each proposal for a potential change or addition to EN 301 549 starts off as an "Issue". Issues can be accessed by selecting "Issues" in the main (side) menu. Each issue will have one or more "labels" assigned to it to show the context of the suggested change and to assist in filtering changes to only view a subset. If an issue proposes a way to resolve the issue, the proposed solution must be consistent [with the design principles that apply to the document](https://labs.etsi.org/rep/HF/en301549/-/wikis/EN-301-549-Design-Principles).
Each proposal for a potential change or addition to EN 301 549 starts off as an "Issue". Issues can be accessed by selecting "Issues" in the main (side) menu. Each issue will have one or more "labels" assigned to it to show the context of the suggested change and to assist in filtering changes to only view a subset. If an issue proposes a way to resolve the issue, the proposed solution must be consistent with [the design principles that apply to the document](https://labs.etsi.org/rep/HF/en301549/-/wikis/EN-301-549-Design-Principles).
A threaded discussion can take place for each issue. Issues can contain links to other resources including "Snippets".
......@@ -25,7 +25,7 @@ A snippet will allow a very realistic looking facsimile of how the proposed revi
# How to participate
* All the activity on the site can be viewed by anyone who has a link to it.
* Anybody can send a proposal for an issue or a comment on an issue to HFsupport@etsi.org. Emails received will be checked and then submitted by a member as a new issue and assigned an appropriate "Label". Please ensure that any proposed ways to resolve an issue are consistent [with the design principles that apply to the document](https://labs.etsi.org/rep/HF/en301549/-/wikis/EN-301-549-Design-Principles).
* Anybody can send a proposal for an issue or a comment on an issue to HFsupport@etsi.org. Emails received will be checked and then submitted by a member as a new issue and assigned an appropriate "Label". Please ensure that any proposed ways to resolve an issue are consistent with [the design principles that apply to the document](https://labs.etsi.org/rep/HF/en301549/-/wikis/EN-301-549-Design-Principles).
* * Anyone who has an ETSI EOL account can directly create and comment on issues within GitLab.
* Whether directly input or submitted by email, each issue should cover a single simple proposal.
* If you wish to submit multiple proposals then please making them separate issues or submit each one as a separate email.
......