Editing Web accessibility (section)

==Web accessibility legislation==
Because of the growth in internet usage<ref name="Internet World Stats Usage and Population Statistics">{{cite web |url=http://www.internetworldstats.com/stats.htm |title=Internet Usage Statistics |publisher=Miniwatts Marketing Group |date=30 June 2014 |access-date=17 December 2014 |archive-date=23 June 2011 |archive-url=https://web.archive.org/web/20110623200007/http://www.internetworldstats.com/stats.htm |url-status=live }}</ref> and its growing importance in everyday life, countries around the world are addressing digital access issues through legislation. One approach is to protect access to websites for people with disabilities by using existing human or civil rights legislation. Some countries, like the U.S., protect access for people with disabilities through the technology procurement process.<ref>{{cite web |url=http://www.ssbbartgroup.com/reference/laws-and-standards/section-508-of-the-rehabilitation-act/ |title=Section 508 of the Rehabilitation Act |publisher=SSB BART Group |author=Timothy Stephen Springer |date=24 February 2010 |access-date=24 August 2015 |archive-date=31 August 2015 |archive-url=https://web.archive.org/web/20150831070308/http://www.ssbbartgroup.com/reference/laws-and-standards/section-508-of-the-rehabilitation-act/ |url-status=dead }}</ref> It is common for nations to support and adopt the Web Content Accessibility Guidelines (WCAG) 2.0 by referring to the guidelines in their legislation.<ref>{{cite web |url=http://webaim.org/articles/laws/world/ |title=World Laws Introduction to Laws Throughout the World |publisher=WebAIM (Web Accessibility in Mind) |access-date=18 December 2014 |archive-date=26 November 2014 |archive-url=https://web.archive.org/web/20141126235203/http://webaim.org/articles/laws/world/ |url-status=live }}</ref><ref>{{cite web |url=http://lflegal.com/2013/05/gaad-legal/ |title=Digital Accessibility Laws Around the Globe |publisher=Law Office of Lainey Feingold |date=9 May 2013 |access-date=17 December 2014 |archive-date=24 December 2014 |archive-url=https://web.archive.org/web/20141224081138/http://lflegal.com/2013/05/gaad-legal/ |url-status=live }}</ref> Compliance with web accessibility guidelines is a legal requirement primarily in North America, Europe, parts of South America and parts of Asia.<ref>{{Cite web|title=What is web accessibility and why is it critical to your website's success?|url=https://www.heliosdesign.com/blog/web/why-web-accessibility-is-critical.html|access-date=2020-09-10|website=Helios Design|language=en|archive-date=30 September 2020|archive-url=https://web.archive.org/web/20200930154508/https://www.heliosdesign.com/blog/web/why-web-accessibility-is-critical.html|url-status=live}}</ref>

'''<big>Argentina</big>'''

Law 26.653 on Accessibility to Information on Web Pages.<ref>{{Cite web |title=Infoleg |url=http://servicios.infoleg.gob.ar/infolegInternet/anexos/175000-179999/175694/norma.htm |access-date=2024-02-23 |website=servicios.infoleg.gob.ar}}</ref> Approved by the [[National Congress of Argentina]] on November 3, 2010. It specifies in its Article 1 that both the National State and its decentralized organisms or those companies that are related in any way with public services or goods, must respect the rules and requirements on accessibility in the design of their web pages. The objective is to facilitate access to contents to all persons with disabilities, in order to guarantee equal opportunities in relation to access to information and to avoid discrimination.

In addition, by Decree 656/2019<ref>{{Cite web |title=BOLETIN OFICIAL REPUBLICA ARGENTINA - ACCESO A LA INFORMACIÓN PÚBLICA - Decreto 656/2019 |url=https://www.boletinoficial.gob.ar/detalleAviso/primera/217000 |access-date=2024-02-23 |website=www.boletinoficial.gob.ar}}</ref> the regulation of the aforementioned Law No. 26,653 is approved and it is reported that the authority in charge of its application will be the ONTI, "Oficina Nacional de Tecnologías de Información" (National Office of Information Technologies).<ref>{{Cite web |date=2017-03-08 |title=Oficina Nacional de Tecnologías de Información |url=https://www.argentina.gob.ar/jefatura/innovacion-publica/onti |access-date=2024-02-23 |website=Argentina.gob.ar |language=es}}</ref> This agency is in charge of assisting and/or advising the individuals and legal entities reached by this Law; in addition to disseminating, approving/updating and also controlling the fulfillment of the accessibility standards and requirements of the web pages; among other functions.

===Australia===
In 2000, an [[Australians|Australian]] blind man won a $20,000 court case against the [[Sydney Organising Committee for the Olympic Games|Sydney Organising Committee of the Olympic Games (SOCOG)]].<ref>{{Cite web|title=Maguire v SOCOG {{!}} Australian Human Rights Commission|url=https://humanrights.gov.au/our-work/disability-rights/maguire-v-socog|access-date=2022-01-11|website=humanrights.gov.au|archive-date=11 January 2022|archive-url=https://web.archive.org/web/20220111225806/https://humanrights.gov.au/our-work/disability-rights/maguire-v-socog|url-status=live}}</ref> This was the first successful case under [[Disability Discrimination Act 1992]] because SOCOG had failed to make their official website, [[Sydney Olympic Games]], adequately accessible to blind users. [[Australian Human Rights Commission|The Human Rights and Equal Opportunity Commission (HREOC)]] also published World Wide Web Access: Disability Discrimination Act Advisory Notes.<ref>{{cite web |url=http://www.hreoc.gov.au/disability_rights/standards/www_3/www_3.html |title=World Wide Web Access: Disability Discrimination Act Advisory Notes ver 4.0 (2010) &#124; Australian Human Rights Commission |publisher=Hreoc.gov.au |date=1 July 2010 |access-date=28 July 2013 |archive-date=31 August 2012 |archive-url=https://web.archive.org/web/20120831085343/http://www.hreoc.gov.au/disability_rights/standards/WWW_3/www_3.html |url-status=live }}</ref> All Governments in Australia also have policies and guidelines that require accessible public websites.

===Brazil===
In [[Brazil]], the federal government published a paper with guidelines for accessibility on 18 January 2005, for public reviewing. On 14 December of the same year, the second version was published, including suggestions made to the first version of the paper. On 7 May 2007, the accessibility guidelines of the paper became compulsory to all federal websites. The current version of the paper, which follows the WCAG 2.0 guidelines, is named '''e-MAG, Modelo de {{not a typo|Acessibilidade}} de Governo Eletrônico''' (Electronic Government Accessibility Model), and is maintained by Brazilian [[Ministry of Planning, Budget, and Management]].

The paper can be viewed and downloaded at its official website.<ref>{{cite web |url=http://www.governoeletronico.gov.br/acoes-e-projetos/e-MAG |title=e-MAG – Modelo de Acessibilidade de Governo Eletrônico |publisher=GovernoEletronico.gov.br |access-date=4 January 2014 |archive-date=4 January 2014 |archive-url=https://web.archive.org/web/20140104210818/http://www.governoeletronico.gov.br/acoes-e-projetos/e-MAG |url-status=live }}</ref>

===Canada===
In 2011, the Government of Canada began phasing in the implementation of a new set of web standards that are aimed at ensuring government websites are accessible, usable, interoperable and optimized for mobile devices. These standards replace Common Look and Feel 2.0 (CLF 2.0) Standards for the Internet.

The first of these four standards, Standard on Web Accessibility<ref>{{cite web|url=http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=23601|title=Standard on Web Accessibility|date=2 August 2011|website=Government of Canada|access-date=4 February 2019|archive-date=23 July 2013|archive-url=https://web.archive.org/web/20130723232132/http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=23601|url-status=live}}</ref> came into full effect on 31 July 2013. The Standard on Web Accessibility follows the [[Web Content Accessibility Guidelines]] (WCAG) 2.0 AA, and contains a list of exclusions that is updated annually. It is accompanied by an explicit Assessment Methodology<ref>{{cite web  |url=http://www.tbs-sct.gc.ca/ws-nw/wa-aw/wa-aw-assess-methd-eng.asp  |title=Assessment Methodology  |publisher=Government of Canada  |access-date=14 December 2014  |date=25 January 2012  |archive-date=16 March 2015  |archive-url=https://web.archive.org/web/20150316075538/http://www.tbs-sct.gc.ca/ws-nw/wa-aw/wa-aw-assess-methd-eng.asp  |url-status=dead  }}</ref> that helps government departments comply. The government also developed the Web Experience Toolkit (WET),<ref>{{cite web  |url=http://www.tbs-sct.gc.ca/ws-nw/wa-aw/wet-boew/index-eng.asp  |title=The Web Experience Toolkit  |publisher=Government of Canada  |access-date=14 December 2014  |date=25 January 2012  |archive-date=10 October 2014  |archive-url=https://web.archive.org/web/20141010030600/http://www.tbs-sct.gc.ca/ws-nw/wa-aw/wet-boew/index-eng.asp  |url-status=dead  }}</ref> a set of reusable web components for building innovative websites.  The WET helps government departments build innovative websites that are accessible, usable and interoperable and therefore comply with the government's standards. The [https://wet-boew.github.io/wet-boew/index.html WET toolkit is open source] and available for anyone to use.

The three related web standards are:  the Standard on Optimizing Websites and Applications for Mobile Devices,<ref>{{cite web |url=http://www.tbs-sct.gc.ca/ws-nw/mo-om/index-eng.asp |title=Standard on Optimizing Websites and Applications for Mobile Devices |publisher=Government of Canada |access-date=14 December 2014 |date=30 April 2013 |archive-date=19 March 2015 |archive-url=https://web.archive.org/web/20150319110300/http://www.tbs-sct.gc.ca/ws-nw/mo-om/index-eng.asp |url-status=dead }}</ref> the Standard on Web Usability<ref>{{cite web |url=http://www.tbs-sct.gc.ca/ws-nw/wu-fe/index-eng.asp |title=Standard on Web Usability |publisher=Government of Canada |access-date=14 December 2014 |date=25 January 2012 |archive-date=19 March 2015 |archive-url=https://web.archive.org/web/20150319110304/http://www.tbs-sct.gc.ca/ws-nw/wu-fe/index-eng.asp |url-status=dead }}</ref> and the Standard on Web Interoperability.<ref>{{cite web |url=http://www.tbs-sct.gc.ca/ws-nw/wi-iw/index-eng.asp |title=Standard on Web Interoperability |publisher=Government of Canada |access-date=14 December 2014 |date=2 August 2012 |archive-date=19 March 2015 |archive-url=https://web.archive.org/web/20150319133436/http://www.tbs-sct.gc.ca/ws-nw/wi-iw/index-eng.asp |url-status=dead }}</ref>

In 2019 the [[Government of Canada]] passed the [[Accessible Canada Act]]. This builds on the on provincial legislation like the [[Accessibility for Ontarians with Disabilities Act, 2005|Accessibility for Ontarians with Disabilities Act]], [[The Accessibility for Manitobans Act]] and the [[Nova Scotia Accessibility Act]].

===European Union===
In February 2014 a draft law was endorsed by the [[European Parliament]] stating that all websites managed by public sector bodies have to be made accessible to everyone.<ref>{{cite web|title=MEPs vote to make online public services accessible to everyone|url=http://www.europarl.europa.eu/news/en/news-room/content/20140220IPR36573/html/MEPs-vote-to-make-online-public-services-accessible-to-everyone |publisher=European Parliament|access-date=28 February 2017|date=26 February 2014|archive-date=24 September 2015|archive-url=https://web.archive.org/web/20150924195259/http://www.europarl.europa.eu/news/en/news-room/content/20140220IPR36573/html/MEPs-vote-to-make-online-public-services-accessible-to-everyone|url-status=live}}</ref>

A [[European Commission]] ''Communication'' on eAccessibility was published on 13 September 2005.<ref name=sec1095 /> The commission's aim to "harmonise and facilitate the [[Government procurement|public procurement]] of accessible ICT products and services" was embedded in a mandate issued to CEN, CENELEC and ETSI in December 2005, reference M 376.<ref>Level Access, [https://www.levelaccess.com/accessibility-regulations/m376/ European Union's Mandate M 376] {{Webarchive|url=https://web.archive.org/web/20211120080336/https://www.levelaccess.com/accessibility-regulations/m376/ |date=20 November 2021 }}, accessed 20 November 2021</ref> A mandate is a request for the drafting and adoption of a European standard or European standardisation deliverables issued to one or more of the European standardisation organisations. Mandates are usually accepted by the standardisation organisation because they are based on preliminary consultation, although technically the organisation is independent and has a right to decline the mandate.<ref>European Commission, [https://ec.europa.eu/growth/single-market/european-standards/standardisation-requests-mandates_en Standardisation requests - mandates] {{Webarchive|url=https://web.archive.org/web/20211120080344/https://ec.europa.eu/growth/single-market/european-standards/standardisation-requests-mandates_en |date=20 November 2021 }}, accessed 20 November 2021</ref> The mandate also called for the development of an electronic toolkit for public procurers enabling them to have access to the resulting harmonised requirements.<ref name=mandate376>European Commission, [https://ec.europa.eu/growth/tools-databases/mandates/index.cfm?fuseaction=select_attachments.download&doc_id=425 Standardisation Mandate to CEN, CENELEC AND ETSI in support of European Accessibility Requirements for Public Procurement of Products and Services in the ICT Domain] {{Webarchive|url=https://web.archive.org/web/20211222221023/https://ec.europa.eu/growth/tools-databases/mandates/index.cfm?fuseaction=select_attachments.download&doc_id=425 |date=22 December 2021 }}, M 376 - EN, published 7 December 2005, accessed 20 November 2021</ref> The commission also noted that the harmonised outcome, while intended for public procurement purposes, might also be useful for [[procurement]] in the private sector.<ref name=mandate376 />{{rp|Section 2.3}}

On 26 October 2016, the European Parliament approved the [[Web Accessibility Directive]], which requires that the websites and mobile apps of public sector bodies be accessible. The relevant accessibility requirements are described in the European standard [[EN 301 549]] V3.2.1 (published by [[ETSI]]). EU member states were expected to bring into force by 23 September 2018 laws and regulations that enforce the relevant accessibility requirements.

* websites of public sector bodies should comply by 23 September 2018; 
* mobile apps by 23 June 2021.

Some categories of websites and apps are excepted from the directive, for example "websites and mobile applications of public service broadcasters and their subsidiaries".<ref>[http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016L2102 Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies] {{Webarchive|url=https://web.archive.org/web/20170329051132/http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016L2102 |date=29 March 2017 }}, EUR-Lex; published in the 'Official Journal of the European Union' on 2 December 2016, accessed 28 March 2017</ref>

The European Commission's "Rolling Plan for ICT Standardisation 2017" notes that ETSI standard EN 301 549 V1.1.2 will need to be updated to add accessibility requirements for mobile applications and evaluation methodologies to test compliance with the standard.<ref>European Commission: Directorate-General for Internal Market, Industry, Entrepreneurship and SMEs: [http://ec.europa.eu/information_society/newsroom/image/document/2017-13/grow_rolling_plan_ict_2017_web_170302_C7EC62EB-0196-6C12-45229D71D00B0D6B_43894.pdf Rolling Plan for ICT Standardisation 2017. COM (2016) 176 final.] {{Webarchive|url=https://web.archive.org/web/20170329051223/http://ec.europa.eu/information_society/newsroom/image/document/2017-13/grow_rolling_plan_ict_2017_web_170302_C7EC62EB-0196-6C12-45229D71D00B0D6B_43894.pdf |date=29 March 2017 }}. Accessed 28 March 2017.</ref>

In 2019 the European Union introduced the [[European Accessibility Act]], as one of the leading pieces of legislation for [[digital accessibility]] and [[digital inclusion]]. The European Accessibility Act (EAA), which [https://ec.europa.eu/social/main.jsp?catId=1202&intPageId=5581&langId=en#:~:text=All%20EU%20Member%20States%20must,by%20the%20Act%20are%20accessible. will enter into force on 28 June 2025], requiring companies to ensure that the newly marketed products and services covered by the Act are accessible. All websites will need to adhere to the WCAG Principles of Perceivable, Operable, Understandable and Robust, and deliver comparative levels of user experience to disabled customers. As of June 28, 2025, customers will be able to file complaints before national courts or authorities if services or products do not respect the new rules.<ref>{{Cite web |title=Employment, Social Affairs & Inclusion |url=https://ec.europa.eu/social/main.jsp?catId=1202&intPageId=5581&langId=en |access-date=June 27, 2024 |website=European Commission}}</ref>

===India===
In [[India]], [[National Informatics Centre]] (NIC), under [[Ministry of Electronics and Information Technology]] (MeitY) has passed [[Guidelines for Indian Government Websites]] (GIGW)<ref>{{cite web |title=Guidelines for Indian Government Websites |url=https://guidelines.india.gov.in/ |website=Guidelines for Indian Government Websites |access-date=19 September 2023}}</ref> for government agencies in 2009, compelling them to adhere to WCAG 2.0 Level A standards.<ref>{{cite web |title=India: Web Accessibility Initiative (WAI)|url=https://www.w3.org/WAI/policies/india/ |website=W3C WAI}}</ref>

[[Ministry of Electronics and Information Technology]] (MeitY) has National Policy on Universal Electronic Accessibility<ref>{{cite journal |title=National Policy on Universal Electronic Accessibility |journal=Ministry of Electronics and Information Technology |date=2009 |page=6|url=https://www.meity.gov.in/writereaddata/files/National%20Policy%20on%20Universal%20Electronics%281%29_0.pdf |access-date=19 September 2023}}</ref> clearly stated, Accessibility Standards and Guidelines be formulated or adapted from prevailing standards in the domain including [[World Wide Web Consortium]] accessibility [[Web standards]] and guidelines such as Authoring Tool Accessibility Guidelines ([[Web Accessibility Initiative#Authoring Tool Accessibility Guidelines (ATAG)|ATAG]]<ref name="Shawn Lawton Henry"/>), [[Web Content Accessibility Guidelines]] (WCAG 2.0) and User Agent Accessibility Guidelines ([[UAAG]]<ref name="w3.org"/>).

GIGW aims to ensure the quality and accessibility of government guidelines by offering guidance on desirable practices covering the entire lifecycle of websites, web portals and web applications, right from conceptualization and design to their development, maintenance and management. The Department of Administrative Reforms and Public Grievances made the same a part of the Central Secretariat Manual of Office Procedure.

GIGW 3.0<ref>{{cite web |title=Introduction |url=https://guidelines.india.gov.in/introduction/ |website=Guidelines for Indian Government Websites |access-date=19 September 2023}}</ref> also significantly enhances the guidance on the accessibility and usability of mobile apps, especially by offering specific guidance to government organizations on how to leverage public digital infrastructure devised for whole-of-government delivery of services, benefits and information.<ref>{{cite journal |title=GIGW |journal=GIGW Manual 3.0 |date=2009 |page=3 |url=https://cdnbbsr.s3waas.gov.in/s3c92a10324374fac681719d63979d00fe/uploads/2023/05/2023051731.pdf |access-date=19 September 2023}}</ref>

The [[Rights of Persons with Disabilities Act, 2016]] (RPwD)<ref>{{cite web |title=The Rights of Persons with Disabilities (RPWD) |url=https://deoc.in/the-rights-of-persons-with-disabilitiesrpwd-act/ |website=Diversity And Equal Opportunity Centre |publisher=DEOC |access-date=19 September 2023}}</ref> passed in parliament. The law replaced earlier legislation and provided clearer guidance for digital accessibility. The RPwD Act, 106 through Sections 40-46 mandates  accessibility to be ensured in all public-centric buildings, transportation systems, Information and Communication Technology (ICT) services, consumer products and all other services being provided by the Government or other service providers.<ref>{{cite journal |title=Rights of Persons with Disabilities Act, 2016 |journal=Legislative Department |date=2016 |pages=36 |url=https://lddashboard.legislative.gov.in/sites/default/files/A2016-49_1.pdf |access-date=19 September 2023}}</ref>

===Ireland===
In [[Ireland]], the Disability Act 2005<ref>{{cite web |url=http://www.oireachtas.ie/viewdoc.asp?DocID=4338&CatID=87 |title=Disability Act 2005 – Tithe an Oireachtais |publisher=Oireachtas.ie |date=13 November 2009 |access-date=28 July 2013 |archive-date=24 November 2012 |archive-url=https://web.archive.org/web/20121124035229/http://www.oireachtas.ie/viewdoc.asp?DocID=4338&CatID=87 |url-status=live }}</ref> requires that where a public body communicates in electronic form with one or more persons, the contents of the communication must be, as far as practicable, "accessible to persons with a visual impairment to whom adaptive technology is available" (Section 28(2)). The National Disability Authority has produced a Code of Practice<ref>{{cite web |url=http://www.nda.ie/cntmgmtnew.nsf/0/3DB134DF72E1846A8025710F0040BF3D?OpenDocument |title=Code of Practice on Accessibility of Public Services and Information Provided by Public Bodies |publisher=Nda.ie |date=21 July 2006 |access-date=28 July 2013 |archive-date=19 August 2013 |archive-url=https://web.archive.org/web/20130819235526/http://www.nda.ie/cntmgmtnew.nsf/0/3DB134DF72E1846A8025710F0040BF3D?OpenDocument |url-status=dead }}</ref> giving guidance to public bodies on how to meet the obligations of the Act. This is an approved code of practice and its provisions have the force of legally binding statutory obligations. It states that a public body can achieve compliance with Section 28(2) by "reviewing existing practices for electronic communications in terms of accessibility against relevant guidelines and standards", giving the example of "Double A conformance with the Web Accessibility Initiative's (WAI) Web Content Accessibility Guidelines (WCAG)".

===Israel===
The Israeli Ministry of Justice recently published regulations requiring Internet websites to comply with Israeli standard 5568, which is based on the W3C Web Content Accessibility Guidelines 2.0. The main differences between the Israeli standard and the W3C standard concern the requirements to provide captions and texts for audio and video media. The Israeli standards are somewhat more lenient, reflecting the current technical difficulties in providing such captions and texts in Hebrew.<ref>{{cite web|url=http://israeltechnologylaw.wordpress.com/2014/03/05/website-accessibility-requirements/|archive-url=https://web.archive.org/web/20140928203000/http://israeltechnologylaw.wordpress.com/2014/03/05/website-accessibility-requirements/|url-status=dead|archive-date=2014-09-28|title=Israel Technology Law Blog, Website Accessibility Requirements}}</ref>

===Italy===
In Italy, web accessibility is ruled by the so-called "[[Stanca Act|Legge Stanca]]" (Stanca Act), formally Act n.4 of 9 January 2004, officially published on the [[Gazzetta Ufficiale]] on 17 January 2004. The original Stanca Act was based on the WCAG 1.0. On 20 March 2013 the standards required by the Stanca Act were updated to the WCAG 2.0.

===Japan===
Web Content Accessibility Guidelines in Japan were established in 2004 as JIS (Japanese Industrial Standards) X 8341–3. JIS X 8341-3 was revised in 2010 as JIS X 8341-3:2010 to encompass WCAG 2.0, and it was revised in 2016 as JIS X 8341-3:2016 to be identical standards with the international standard ISO/IEC 40500:2012. The Japanese organization WAIC (Web Accessibility Infrastructure Committee) has published the history and structure of JIS X 8341-3:2016.<ref>{{cite web|title=JIS X 8341-3:2016|url=https://waic.jp/docs/jis2016/understanding/201604/|website=waic.jp|publisher=Web Accessibility Infrastructure Commission|access-date=17 May 2023|language=ja|archive-date=17 May 2023|archive-url=https://web.archive.org/web/20230517083205/https://waic.jp/docs/jis2016/understanding/201604/|url-status=live}}</ref>

===Malta===
In Malta Web Content Accessibility assessments were carried out by the Foundation for Information Technology Accessibility (FITA) since 2003.<ref>{{cite web|url=https://fitamalta.eu/15-years-of-service-projects-and-innovation/|title=FITA - 15 years of service,projects and innovation|access-date=23 August 2020|archive-date=29 December 2020|archive-url=https://web.archive.org/web/20201229075046/https://fitamalta.eu/15-years-of-service-projects-and-innovation/|url-status=live}}</ref> Until 2018, this was done in conformance with the requirements of the Equal Opportunities Act (2000) CAP 43 and applied WACG guidelines.<ref>{{cite web|url=https://fitamalta.eu/fita-services/consultancy-services/|title=FITA Services|access-date=23 August 2020|archive-date=29 December 2020|archive-url=https://web.archive.org/web/20201229070613/https://fitamalta.eu/fita-services/consultancy-services/|url-status=live}}</ref> With the advent of the EU Web Accessibility Directive the Malta Communications Authority was charged with ensuring the accessibility of online resources owned by Maltese public entities.<ref>{{cite web|url=https://www.mca.org.mt/webaccessibility|title=MCA - Web Accessibility|date=14 December 2018|access-date=23 August 2020|archive-date=11 August 2020|archive-url=https://web.archive.org/web/20200811035109/https://www.mca.org.mt/webaccessibility|url-status=live}}</ref> FITA continues to provide ICT accessibility assessments to public and commercial entities, applying standard EN301549 and WCAG 2.1 as applicable.  Therefore, both the Equal Opportunities Act anti-discrimination legislation and the transposed EU Web Accessibility Directive are applicable to the Maltese scenario.

===Norway===
In Norway, web accessibility is a legal obligation under the Act 20 June 2008 No 42 relating to a prohibition against discrimination on the basis of disability, also known as the [[Anti-discrimination Accessibility Act]]. The Act went into force in 2009, and the Ministry of Government Administration, Reform and Church Affairs [Fornyings-, administrasjons- og kirkedepartementet] published the Regulations for universal design of information and communication technology (ICT) solutions [Forskrift om universell utforming av informasjons- og kommunikasjonsteknologiske (IKT)-løsninger] in 2013.<ref>{{cite web|title=Regulation for universal design of information and communication technology (ICT) solutions|url=https://www.regjeringen.no/en/dokumenter/regulation-universal-design-ict/id731520/|publisher=Ministry of Local Government and Modernisation|access-date=10 November 2016|date=21 June 2013|archive-date=11 November 2016|archive-url=https://web.archive.org/web/20161111124230/https://www.regjeringen.no/en/dokumenter/regulation-universal-design-ict/id731520/|url-status=live}}</ref> The regulations require compliance with Web Content Accessibility Guidelines 2.0 (WCAG 2.0) / NS / ISO / IEC 40500: 2012, level A and AA with some exceptions.<ref>{{cite journal|last1=Giannoumis|first1=G. Anthony|title=Regulating Web Content: the nexus of legislation and performance standards in the United Kingdom and Norway|journal=Behavioral Sciences & the Law|date=2014|volume=32|issue=1|pages=52–75|doi=10.1002/bsl.2103|pmid=24504974|hdl=10642/2585|hdl-access=free}}</ref><ref>{{cite web|title=Forskrift om universell utforming av informasjon|url=http://lovdata.no/dokument/SF/forskrift/2013-06-21-732?q=Forskrift%20om%20universell%20utforming%20av*1/3Forskriftomuniversellutformingavinformasjons-ogkommunikasjonsteknologiske|website=Lovdata|access-date=6 November 2014|archive-date=6 November 2014|archive-url=https://web.archive.org/web/20141106105319/http://lovdata.no/dokument/SF/forskrift/2013-06-21-732?q=Forskrift%20om%20universell%20utforming%20av%2A1%2F3Forskriftomuniversellutformingavinformasjons-ogkommunikasjonsteknologiske|url-status=live}}</ref> The Norwegian Agency for Public Management and eGovernment (Difi) is responsible for overseeing that ICT solutions aimed at the general public are in compliance with the legislative and regulatory requirements.<ref>{{cite web|title=The Government's Action Plan for Universal Design 2015–2019|url=https://www.regjeringen.no/contentassets/565cb331b0ee4bb4b997157a543a51d4/the-governments-action-plan-for-universal-design-20152019_q-1233-e.pdf#page=26|publisher=Norwegian Ministry of Children, Equality and Social Inclusion|access-date=10 November 2016|archive-date=11 November 2016|archive-url=https://web.archive.org/web/20161111124147/https://www.regjeringen.no/contentassets/565cb331b0ee4bb4b997157a543a51d4/the-governments-action-plan-for-universal-design-20152019_q-1233-e.pdf#page=26|url-status=live}}</ref>

===Philippines===
As part of the [[Web Accessibility Initiatives in the Philippines]], the government through the National Council for the Welfare of Disabled Persons (NCWDP) board approved the recommendation of forming an ad hoc or core group of webmasters that will help in the implementation of the [[Biwako Millennium Framework]] set by the [[UNESCAP]].

The [[Philippines]] was also the place where the Interregional Seminar and Regional Demonstration Workshop on Accessible Information and Communications Technologies (ICT) to Persons with Disabilities was held where eleven countries from Asia – Pacific were represented. The [[Manila Accessible Information and Communications Technologies Design Recommendations]] was drafted and adopted in 2003.

===Spain===
In Spain, UNE 139803:2012 is the norm entrusted to regulate web accessibility. This standard is based on Web Content Accessibility Guidelines 2.0.<ref>{{Cite web|title=UNE 139803:2012 Requisitos de accesibilidad para contenidos en...|url=https://www.en.une.org/encuentra-tu-norma/busca-tu-norma/norma/?c=N0049614|website=www.en.une.org|access-date=2020-05-05|archive-date=24 October 2020|archive-url=https://web.archive.org/web/20201024205823/https://www.en.une.org/encuentra-tu-norma/busca-tu-norma/norma/?c=N0049614|url-status=live}}</ref>

===Sweden===
In Sweden, Verva, the Swedish Administrative Development Agency is responsible for a set of guidelines for Swedish public sector web sites. Through the guidelines, web accessibility is presented as an integral part of the overall development process and not as a separate issue. The Swedish guidelines contain criteria which cover the entire life cycle of a website; from its conception to the publication of live web content. These criteria address several areas which should be considered, including:
* accessibility
* usability
* web standards
* privacy issues
* information architecture
* developing content for the web
* Content Management Systems (CMS) / authoring tools selection.
* development of web content for mobile devices.

An English translation was released in April 2008: Swedish National Guidelines for Public Sector Websites.<ref>{{cite web|title=Swedish National Guidelines for Public Sector Websites|url=http://arkiv.edelegationen.se/verva/upload/english/swedish-guidelines-public-sector-websites.pdf|website=arkiv.edelegationen.se|publisher=VERVA|date=April 2008|access-date=15 January 2015|archive-date=3 March 2016|archive-url=https://web.archive.org/web/20160303222043/http://arkiv.edelegationen.se/verva/upload/english/swedish-guidelines-public-sector-websites.pdf|url-status=live}}</ref> The translation is based on the latest version of Guidelines which was released in 2006.<ref>{{cite web |url=http://www.standards-schmandards.com/2006/swe-guidelines/ |title=New Version of Guidelines for Swedish Public Sector Web Sites |year=2006 |author=Peter Krantz |publisher=standards-schmandards.com |access-date=18 December 2012 |archive-date=23 January 2013 |archive-url=https://web.archive.org/web/20130123194407/http://www.standards-schmandards.com/2006/swe-guidelines/ |url-status=live }}</ref>

===United Kingdom===
In the [[UK]], the [[Equality Act 2010]] does not refer explicitly to website accessibility, but makes it illegal to discriminate against people with disabilities. The Act applies to anyone providing a service; public, private and voluntary sectors. The ''Code of Practice: Rights of Access – Goods, Facilities, Services and Premises'' document<ref>{{cite web |url=http://www.equalityhumanrights.com/uploaded_files/pas78.pdf |title=A guide to good practice in commissioning accessible websites |publisher=Equality and Human Rights Commission |access-date=18 December 2012 |archive-date=10 June 2012 |archive-url=https://web.archive.org/web/20120610191541/http://equalityhumanrights.com/uploaded_files/pas78.pdf |url-status=live }}</ref> published by the government's [[Equality and Human Rights Commission]] to accompany the Act does refer explicitly to websites as one of the "services to the public" which should be considered covered by the Act.

In December 2010 the UK released the standard ''[[BS 8878|BS 8878:2010 Web accessibility. Code of practice]]''. This standard effectively supersedes PAS 78 (pub. 2006).  PAS 78, produced by the [[Disability Rights Commission]] and usable by disabled people. The standard has been designed to introduce non-technical professionals to improved accessibility, usability and user experience for disabled and older people.<ref>{{cite web|title=BS 8878:2010 Web accessibility. Code of practice|url=http://shop.bsigroup.com/ProductDetail/?pid=000000000030180388|publisher=[[British Standards Institute]]|access-date=15 January 2015|archive-date=23 December 2014|archive-url=https://web.archive.org/web/20141223153732/http://shop.bsigroup.com/ProductDetail/?pid=000000000030180388|url-status=live}}</ref> It will be especially beneficial to anyone new to this subject as it gives guidance on process, rather than on technical and design issues. BS 8878 is consistent with the [[Equality Act 2010]]<ref>{{cite web |url=http://www.legislation.gov.uk/ukpga/2010/15/contents |title=Equality Act 2010 |publisher=Legislation.gov.uk |access-date=28 July 2013 |archive-date=1 April 2011 |archive-url=http://webarchive.loc.gov/all/20110401110633/http%3A//www.legislation.gov.uk/ukpga/2010/15/contents |url-status=live }}</ref> and is referenced in the UK government's e-Accessibility Action Plan as the basis of updated advice on developing accessible online services. It includes recommendations for:

* Involving disabled people in the development process and using automated tools to assist with accessibility testing
* The management of the guidance and process for upholding existing accessibility guidelines and specifications.

BS 8878 is intended for anyone responsible for the policies covering web product creation within their organization, and governance against those policies. It additionally assists people responsible for promoting and supporting equality and inclusion initiatives within organizations and people involved in the procurement, creation or training of web products and content. A summary of BS 8878<ref>{{cite web |url=http://www.hassellinclusion.com/bs8878/ |title=BS 8878 web accessibility standards – all you need to know |publisher=Hassell Inclusion |access-date=28 July 2013 |archive-date=12 August 2013 |archive-url=https://web.archive.org/web/20130812122647/http://www.hassellinclusion.com/bs8878/ |url-status=live }}</ref> is available to help organisations better understand how the standard can help them embed accessibility and inclusive design in their business-as-usual processes.

On 28 May 2019, BS 8878 was superseded by ISO 30071-1, the international Standard that built on BS 8878 and expanded it for international use. A summary of how ISO 30071-1 relates to BS 8878<ref>{{cite web |url=https://www.hassellinclusion.com/iso-30071-1/ |title=ISO 30071-1 digital accessibility standards (supersedes BS 8878) – all you need to know |publisher=Hassell Inclusion |access-date=28 May 2019 |archive-date=27 May 2019 |archive-url=https://web.archive.org/web/20190527162649/https://www.hassellinclusion.com/iso-30071-1/ |url-status=live }}</ref> is available to help organisations understand the new Standard.

On April 9, [[National Rail]] replaced its blue and white aesthetic with a black and white theme, which was criticized for not conforming to the Web Content Accessibility Guidelines. The company restored the blue and white theme and said it is investing in modernising its website in accords to the latest accessibility guidelines.<ref>{{Cite web|url=https://www.independent.co.uk/life-style/gadgets-and-tech/national-rail-prince-philip-death-black-grey-b1830257.html|title=Prince Philip: National Rail's 'accessibility process' failed to see …|website=[[Independent.co.uk]] |access-date=19 May 2022|archive-date=13 April 2021|archive-url=https://archive.today/20210413081114/https://www.independent.co.uk/life-style/gadgets-and-tech/national-rail-prince-philip-death-black-grey-b1830257.html|url-status=bot: unknown}}</ref>

In 2019 new accessibility regulations<ref>{{Cite web|title=Regulations on the accessibility of new public sector websites come into force|url=https://www.gov.uk/government/news/regulations-on-the-accessibility-of-new-public-sector-websites-come-into-force|access-date=2021-09-03|website=GOV.UK|language=en|archive-date=1 September 2021|archive-url=https://web.archive.org/web/20210901124401/https://www.gov.uk/government/news/regulations-on-the-accessibility-of-new-public-sector-websites-come-into-force|url-status=live}}</ref><ref>{{Cite web|title=Understanding accessibility requirements for public sector bodies|url=https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps|access-date=2021-09-03|website=GOV.UK|language=en|archive-date=3 September 2021|archive-url=https://web.archive.org/web/20210903213503/https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps|url-status=live}}</ref> came into force setting a legal duty for public sector bodies to publish accessibility statements and make their websites accessible by 23 September 2020 <ref>{{Cite web|title=Understanding new accessibility requirements for public sector bodies {{!}} Local Government Association|url=https://www.local.gov.uk/our-support/accessibility|access-date=2021-09-03|website=www.local.gov.uk|language=en|archive-date=3 September 2021|archive-url=https://web.archive.org/web/20210903213505/https://www.local.gov.uk/our-support/accessibility|url-status=live}}</ref> Accessibility statements include information about how the website was tested  and the organisation's plan to fix any accessibility problems. Statements should be published and linked to on every page on the website.<ref>{{Cite web|title=Accessibility Regulations for Public Sector Bodies|url=https://accessibility.campaign.gov.uk/|access-date=2021-09-03|website=accessibility.campaign.gov.uk|language=en-GB|archive-date=3 September 2021|archive-url=https://web.archive.org/web/20210903213510/https://accessibility.campaign.gov.uk/|url-status=live}}</ref>

===United States===
In the [[United States]], [[Section 508 Amendment to the Rehabilitation Act of 1973]] requires all Federal agencies' electronic and information technology to be accessible to those with disabilities. Both members of the public and federal employees have the right to access this technology, such as computer hardware and software, websites, phone systems, and copiers.<ref>{{cite web|url=https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards|title=About the Section 508 Standards – United States Access Board|first=Dave|last=Yanchulis|website=www.access-board.gov|access-date=18 March 2018|archive-date=22 March 2018|archive-url=https://web.archive.org/web/20180322141909/https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards|url-status=live}}</ref>  
Also, [[Section 504 of the Rehabilitation Act]] prohibits discrimination on the basis of disability for entities receiving federal funds and has been cited in multiple lawsuits against organizations such as hospitals that receive federal funds through medicare/medicaid.

In addition, [[Americans with Disabilities Act of 1990#Title III—public accommodations (and commercial facilities)|Title III of the Americans with Disabilities Act (ADA)]] prohibits discrimination on the basis of disability.  There is some debate on the matter; multiple courts and the U.S. Department of Justice have taken the position that the ADA requires website and app operators and owners to take affirmative steps to make their websites and apps accessible to disabled persons and compatible with common assistive technologies such as the JAWS screen reader, while other courts have taken the position that the ADA does not apply online.  The U.S. Department of Justice has endorsed the WCAG2.0AA standard as an appropriate standard for accessibility in multiple settlement agreements.<ref>{{cite web|url=https://www.ada.gov/regs2010/titleIII_2010/titleIII_2010_regulations.htm|title=Nondiscrimination on the Basis of Disability in Public Accommodations and Commercial Facilities|website=www.ada.gov|date=8 March 2012 |access-date=14 May 2018|archive-date=18 May 2018|archive-url=https://web.archive.org/web/20180518160944/https://www.ada.gov/regs2010/titleIII_2010/titleIII_2010_regulations.htm|url-status=live}}</ref>

Numerous lawsuits challenging websites and mobile apps on the basis of the ADA have been filed since 2017. These cases appears spurred by a 2017 case, ''Gil v. Winn Dixie Stores'', in which a federal court in Florida ruled that [[Winn Dixie]]'s website must be accessible. Around 800 cases related to web accessibility were filed in 2017, and over 2,200 were filed in 2018. Additionally, though the Justice Department had stated in 2010 that they would publish guidelines for web accessibility, they reversed this plan in 2017, also spurring legal action against inaccessible sites.<ref name="dominos"/>

A notable lawsuit related to the ADA was filed against [[Domino's Pizza]] by a blind user who could not use Domino's mobile app. At the federal district level, the court ruled in favor of Domino's as the Justice Department had not established the guidelines for accessibility, but this was appealed to the [[Ninth Circuit]]. The Ninth Circuit overruled the district court, ruling that because Domino's is a brick-and-mortar store, which must meet the ADA, and the mobile app an extension of their services, their app must also be compliant with the ADA. Domino's petitioned to the Supreme Court, backed by many other restaurants and retail chains, arguing that this decision impacts their [[Due Process Clause|Due Process]] since disabled customers have other, more accessible means to order.<ref name="dominos">{{cite web | url = https://www.cnbc.com/2019/07/25/dominos-asks-supreme-court-to-say-disability-protections-dont-apply-online.html | title = A blind man couldn't order pizza from Domino's. The company wants the Supreme Court to say websites don't have to be accessible | first = Tucker | last = Higgens | date = 25 July 2019 | access-date = 1 August 2019 | work = [[CNBC]] | archive-date = 30 July 2019 | archive-url = https://web.archive.org/web/20190730025336/https://www.cnbc.com/2019/07/25/dominos-asks-supreme-court-to-say-disability-protections-dont-apply-online.html | url-status = live }}</ref> In October 2019, the Supreme Court declined to hear the case, which effectively upheld the decision of the 9th Circuit Court and requires the case to be heard as it stands.<ref>{{cite web |title=Robles v. Domino's Pizza LLC |url=https://adasoutheast.org/court/robles-v-dominos-pizza-llc/ |website=Information, Guidance and Training on the Americans with Disabilities Act |publisher=Southeast ADA Center |access-date=22 June 2022 |archive-url=https://web.archive.org/web/20220408074426/https://adasoutheast.org/court/robles-v-dominos-pizza-llc/ |archive-date=8 April 2022 |location=Syracuse University |date=23 June 2021}}</ref><ref>{{Cite web|url = https://equidox.co/blog/robles-vs-dominos-pizza-explained-no-published-guidelines-doesnt-mean-no-standards/|title = Robles v. Domino's Pizza Explained|date = 18 October 2019|access-date = 27 January 2020|archive-date = 19 May 2022|archive-url = https://web.archive.org/web/20220519225329/https://equidox.co/blog/robles-v-dominos-pizza-explained-no-published-guidelines-doesnt-mean-no-standards/|url-status = live}}</ref>

The number and cost of federal accessibility lawsuits has risen dramatically in the last few years.<ref>{{Cite web|title=Number Of Federal Website Accessibility Lawsuits Nearly Triple, Exceeding 2250 In 2018|url=https://www.adatitleiii.com/2019/01/number-of-federal-website-accessibility-lawsuits-nearly-triple-exceeding-2250-in-2018/|date=2019-01-31|website=ADA Title III|language=en-US|access-date=2020-05-14|archive-date=18 May 2020|archive-url=https://web.archive.org/web/20200518095813/https://www.adatitleiii.com/2019/01/number-of-federal-website-accessibility-lawsuits-nearly-triple-exceeding-2250-in-2018/|url-status=live}}</ref>