Web Accessibility

Web accessibility is the inclusive practice of ensuring there are no barriers that prevent interaction with, or access to websites, by people with disabilities. When sites are correctly designed, developed and edited, generally all users have equal access to information and functionality.

For example, when a site is coded with semantically meaningful HTML, with textual equivalents provided for images and with links named meaningfully, this helps blind users using text-to-speech software and/or text-to-Braille hardware. When text and images are large and/or enlargeable, it is easier for users with poor sight to read and understand the content. When links are underlined (or otherwise differentiated) as well as colored, this ensures that color blind users will be able to notice them. When clickable links and areas are large, this helps users who cannot control a mouse with precision. When pages are not coded in a way that hinders navigation by means of the keyboard alone, or a single switch access device alone, this helps users who cannot use a mouse or even a standard keyboard. When videos are closed captioned or a sign language version is available, deaf and hard-of-hearing users can understand the video. When flashing effects are avoided or made optional, users prone to seizures caused by these effects are not put at risk. And when content is written in plain language and illustrated with instructional diagrams and animations, users with dyslexia and learning difficulties are better able to understand the content. When sites are correctly built and maintained, all of these users can be accommodated without decreasing the usability of the site for non-disabled users.

The needs that Web accessibility aims to address include:

Assistive technologies used for web browsing

Individuals living with a disability use assistive technologies such as the following to enable and assist web browsing:

  • Screen reader software, which can read out, using synthesized speech, either selected elements of what is being displayed on the monitor (helpful for users with reading or learning difficulties), or which can read out everything that is happening on the computer (used by blind and vision impaired users).
  • Braille terminals, consisting of a refreshable braille display which renders text as braille characters (usually by means of raising pegs through holes in a flat surface) and either a mainstream keyboard or a braille keyboard.
  • Screen magnification software, which enlarges what is displayed on the computer monitor, making it easier to read for vision impaired users.
  • Speech recognition software that can accept spoken commands to the computer, or turn dictation into grammatically correct text - useful for those who have difficulty using a mouse or a keyboard.
  • Keyboard overlays, which can make typing easier or more accurate for those who have motor control difficulties.
  • Access to subtitled or sign language videos for deaf people.

Guidelines on accessible web design

Web Content Accessibility Guidelines

In 1999 the Web Accessibility Initiative, a project by the World Wide Web Consortium (W3C), published the Web Content Accessibility Guidelines WCAG 1.0.

On 11 December 2008, the WAI released the WCAG 2.0 as a Recommendation. WCAG 2.0 aims to be up to date and more technology neutral. Though web designers can choose either standard to follow, the WCAG 2.0 have been widely accepted as the definitive guidelines on how to create accessible websites. Governments are steadily adopting the WCAG 2.0 as the accessibility standard for their own websites.[1] In 2012, the Web Content Accessibility Guidelines were also published as an ISO/IEC standard: "ISO/IEC 40500:2012: Information technology -- W3C Web Content Accessibility Guidelines (WCAG) 2.0".[2]

Criticism of WAI guidelines

There has been some criticism of the W3C process, claiming that it does not sufficiently put the user at the heart of the process.[3] There was a formal objection to WCAG's original claim that WCAG 2.0 will address requirements for people with learning disabilities and cognitive limitations headed by Lisa Seeman and signed by 40 organizations and people.[4] In articles such as "WCAG 2.0: The new W3C guidelines evaluated",[5] "To Hell with WCAG 2.0"[6] and "Testability Costs Too Much",[7] the WAI has been criticised for allowing WCAG 1.0 to get increasingly out of step with today's technologies and techniques for creating and consuming web content, for the slow pace of development of WCAG 2.0, for making the new guidelines difficult to navigate and understand, and other argued failings.

Other guidelines


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[8] came into full effect on July 31, 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[9] that helps government departments comply. The government also developed the Web Experience Toolkit (WET),[10] 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 WET 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,[11] the Standard on Web Usability[12] and the Standard on Web Interoperability.[13]


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 adhoc 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.


In Spain, UNE 139803 is the norm entrusted to regulate web accessibility. This standard is based on Web Content Accessibility Guidelines 1.0.[14]


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 lifecycle 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.[15] The translation is based on the latest version of Guidelines which was released in 2006.[16]

United Kingdom

In December 2010 the UK released the standard 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 sable 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.[17] 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[18] 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[19] is available to help organisations better understand how the standard can help them embed accessibility and inclusive design in their business-as-usual processes.


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 to adopt WCAG 2.0. The new version, published by the Web Accessibility Infrastructure Commission (WAIC), has the same four principles, 12 guidelines, and 61 success criteria as WCAG 2.0 has.[20]

Essential components of web accessibility

The accessibility of websites relies on the cooperation of eight components:[21]

  1. The website itself - natural information (text, images and sound) and the markup code that defines its structure and presentation
  2. User agents, such as web browsers and media players
  3. Assistive technologies, such as screen readers and input devices used in place of the conventional keyboard and mouse
  4. Users' knowledge and experience using the web
  5. Developers
  6. Authoring tools
  7. Evaluation tools
  8. Paste new free code in your sites as per Govt guidelines because this language tool increases accessibility of sites for rural, regional and disable people. [22]
  9. a defined web accessibility standard, or a policy for your organization (against which to evaluate the accessibility)

These components interact with each other to create an environment that is accessible to people with disabilities.

Web developers usually use authoring tools and evaluation tools to create Web content.
People ("users") use Web browsers, media players, assistive technologies or other "user agents" to get and interact with the content.[21]

Guidelines for different components

Authoring Tool Accessibility Guidelines (ATAG)

  • ATAG[23] contains 28 checkpoints that provide guidance on:
    • producing accessible output that meets standards and guidelines
    • promoting the content author for accessibility-related information
    • providing ways of checking and correcting inaccessible content
    • integrating accessibility in the overall look and feel
    • making the authoring tool itself accessible to people with disabilities

Web Content Accessibility Guidelines (WCAG)

  • WCAG 1.0: 14 guidelines that are general principles of accessible design
  • WCAG 2.0: 4 principles that form the foundation for web accessibility; 12 guidelines (untestable) that are goals for which authors should aim; and 65 testable success criteria.[24] The W3C's Techniques for WCAG 2.0[25] is a list of techniques that support authors to meet the guidelines and success criteria. The techniques are periodically updated whereas the principles, guidelines and success criteria are stable and do not change.[26]

User Agent Accessibility Guidelines (UAAG)

  • UAAG[27] contains a comprehensive set of checkpoints that cover:
    • access to all content
    • user control over how content is rendered
    • user control over the user interface
    • standard programming interfaces

Web accessibility legislation

Because of the growth in internet usage[28] 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.[29] 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.[30][31][32]


In 2000, an Australian blind man won a $20,000 court case against the Sydney Organizing Committee of the Olympic Games (SOCOG). 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. The Human Rights and Equal Opportunity Commission (HREOC) also published World Wide Web Access: Disability Discrimination Act Advisory Notes.[33] All Governments in Australia also have policies and guidelines that require accessible public websites; Vision Australia maintain a complete list of Australian web accessibility policies.


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 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.[34]

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.[35]

On 26 October 2016, the European Parliament accepted a directive that 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 V1.1.2 (published by ETSI). EU member states are 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".[36]

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.[37]


In Ireland, the Disability Act 2005[38] 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[39] 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)".


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.[40]


In Italy, web accessibility is ruled by the so-called "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.


In Norway, web accessibility is a legal obligation under the Act June 20, 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.[41] 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.[42][43] 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.[44]

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[45] 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.

United States of America

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.[46] 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, 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.[47][48]

Website accessibility audits

A growing number of organizations, companies and consultants offer website accessibility audits. These audits, a type of system testing, identify accessibility problems that exist within a website, and provide advice and guidance on the steps that need to be taken to correct these problems.

A range of methods are used to audit websites for accessibility:

  • Automated tools are available which can identify some of the problems that are present. Depending on the tool the result may vary widely making it difficult to compare test results.[49]
  • Expert technical reviewers, knowledgeable in web design technologies and accessibility, can review a representative selection of pages and provide detailed feedback and advice based on their findings.
  • User testing, usually overseen by technical experts, involves setting tasks for ordinary users to carry out on the website, and reviewing the problems these users encounter as they try to carry out the tasks.

Each of these methods has its strengths and weaknesses:

  • Automated tools can process many pages in a relatively short length of time, but can only identify some of the accessibility problems that might be present in the website.
  • Technical expert review will identify many of the problems that exist, but the process is time consuming, and many websites are too large to make it possible for a person to review every page.
  • User testing combines elements of usability and accessibility testing, and is valuable for identifying problems that might otherwise be overlooked, but needs to be used knowledgeably to avoid the risk of basing design decisions on one user's preferences.

Ideally, a combination of methods should be used to assess the accessibility of a website.

Remediating inaccessible websites

Once an accessibility audit has been conducted, and accessibility errors have been identified, the errors will need to be remediated in order to ensure the site is compliant with accessibility errors. The traditional way of correcting an inaccessible site is to go back into the source code, reprogram the error, and then test to make sure the bug was fixed. If the website is not scheduled to be revised in the near future, that error (and others) would remain on the site for a lengthy period of time, possibly violating accessibility guidelines. Because this is a complicated process, many website owners choose to build accessibility into a new site design or re-launch, as it can be more efficient to develop the site to comply with accessibility guidelines, rather than to remediate errors later.

Accessible Web applications and WAI-ARIA

For a Web page to be accessible all important semantics about the page's functionality must be available so that assistive technology can understand and process the content and adapt it for the user. However, as content becomes more and more complex, the standard HTML tags and attributes become inadequate in providing semantic reliably. Modern Web applications often apply scripts to elements to control their functionality and to enable them to act as a control or other dynamic component. These custom components or widgets do not provide a way to convey semantic information to the user agent. WAI-ARIA (Accessible Rich Internet Applications) is a specification[50] published by the World Wide Web Consortium that specifies how to increase the accessibility of dynamic content and user interface components developed with Ajax, HTML, JavaScript and related technologies. ARIA enables accessibility by enabling the author to provide all the semantics to fully describe its supported behaviour. It also allows each element to expose its current states and properties and its relationships between other elements. Accessibility problems with the focus and tab index are also corrected.

See also


  1. ^ Mark Rogers (2012-11-13). "Government Accessibility Standards and WCAG 2.0". Powermapper.com. Retrieved .
  2. ^ ISO: ISO/IEC 40500:2012: Information technology -- W3C Web Content Accessibility Guidelines (WCAG) 2.0.
  3. ^ Jonathan Chetwynd (24 July 2007). "Putting the User at the Heart of the W3C Process". JISC CETIS. Retrieved 2015.
  4. ^ Lisa Seeman (20 June 2006). "Formal Objection to WCAG 2.0". W3C Public Mailing List Archives. Retrieved .
  5. ^ Trenton Moss says:. "WCAG 2.0: The new W3C accessibility guidelines evaluated". Webcredible.co.uk. Retrieved .
  6. ^ Joe Clark (2013-07-11). "To Hell with WCAG 2 · An A List Apart Article". Alistapart.com. Retrieved .
  7. ^ Gian Sampson-Wild (2013-07-11). "Testability Costs Too Much · An A List Apart Article". Alistapart.com. Retrieved .
  8. ^ "Standard on Web Accessibility". Government of Canada. Retrieved .
  9. ^ "Assessment Methodology". Government of Canada. Retrieved .
  10. ^ "The Web Experience Toolkit". Government of Canada. Retrieved .
  11. ^ "Standard on Optimizing Websites and Applications for Mobile Devices". Government of Canada. Retrieved .
  12. ^ "Standard on Web Usability". Government of Canada. Retrieved .
  13. ^ "Standard on Web Interoperability". Government of Canada. Retrieved .
  14. ^ "La norma UNE 139803:2004 constituye la base de la certificación en Accesibilidad Web" (in Spanish). INTECO. Retrieved .
  15. ^ "Swedish National Guidelines for Public Sector Websites" (pdf). arkiv.edelegationen.se. VERVA. April 2008.
  16. ^ Peter Krantz (2006). "New Version of Guidelines for Swedish Public Sector Web Sites". www.standards-schmandards.com. Retrieved .
  17. ^ "BS 8878:2010 Web accessibility. Code of practice". British Standards Institute. Retrieved 2015.
  18. ^ "Equality Act 2010". Legislation.gov.uk. Retrieved .
  19. ^ "BS 8878 web accessibility standards - all you need to know". Hassell Inclusion. Retrieved .
  20. ^ "JIS X 8341-3:2010". waic.jp (in Japanese). Web Accessibility Infrastructure Commission. Retrieved 2015.
  21. ^ a b Shawn Lawton Henry (August 2005). "Essential Components of Web Accessibility". World Wide Web Consortium. Retrieved .
  22. ^ Sanjeev Kumar (August 2007). "Paste new free code in your sites as per Govt guidelines because this language tool increases accessibility of sites for rural, regional and disable people". atoall. Retrieved .
  23. ^ Shawn Lawton Henry (December 2008). "Authoring Tool Accessibility Guidelines (ATAG) Overview". World Wide Web Consortium. Retrieved .
  24. ^ "Web Content Accessibility Guidelines (WCAG) 2.0". W3C. Retrieved .
  25. ^ "Techniques for WCAG 2.0". W3C. Retrieved .
  26. ^ "Understanding Techniques for WCAG Success Criteria". W3C. Retrieved .
  27. ^ Shawn Lawton Henry (July 2005). "User Agent Accessibility Guidelines (UAAG) Overview". World Wide Web Consortium. Retrieved .
  28. ^ "Internet Usage Statistics". Miniwatts Marketing Group. 2014-06-30. Retrieved .
  29. ^ Timothy Stephen Springer (2010-02-24). "Section 508 of the Rehabilitation Act". SSB BART Group. Retrieved .
  30. ^ "World Laws Introduction to Laws Throughout the World". WebAIM (Web Accessibility in Mind).
  31. ^ "Digital Accessibility Laws Around the Globe". Law Office of Lainey Feingold. 2013-05-09. Retrieved .
  32. ^ Ken Nakata (2013-07-18). "Deadlines Loom for Canada's Web Accessibility Laws". HiSoft. Retrieved .
  33. ^ "World Wide Web Access: Disability Discrimination Act Advisory Notes ver 4.0 (2010) | Australian Human Rights Commission". Hreoc.gov.au. 2010-07-01. Retrieved .
  34. ^ "e-MAG - Modelo de Acessibilidade de Governo Eletrônico". GovernoEletronico.gov.br. Retrieved .
  35. ^ "MEPs vote to make online public services accessible to everyone". www.europarl.europa.eu. European Parliament. 26 February 2014. Retrieved 2017.
  36. ^ 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, EUR-Lex; published in the 'Official Journal of the European Union' on 2.12.2016. Accessed 28.03.2017.
  37. ^ European Commission: Directorate-General for Internal Market, Industry, Entrepreneurship and SMEs: Rolling Plan for ICT Standardisation 2017. COM (2016) 176 final.. Accessed 28.03.2017.
  38. ^ "Disability Act 2005 - Tithe an Oireachtais". Oireachtas.ie. 2009-11-13. Retrieved .
  39. ^ "Code of Practice on Accessibility of Public Services and Information Provided by Public Bodies". Nda.ie. 2006-07-21. Retrieved .
  40. ^ "Israel Technology Law Blog, Website Accessibility Requirements".
  41. ^ "Regulation for universal design of information and communication technology (ICT) solutions". Ministry of Local Government and Modernisation. Retrieved 2016.
  42. ^ Giannoumis, G. Anthony (2014). "Regulating Web Content: the nexus of legislation and performance standards in the United Kingdom and Norway". Behavioral Sciences & the Law. 32 (1): 52-75. doi:10.1002/bsl.2103.
  43. ^ "Forskrift om universell utforming av informasjon". Lovdata. Retrieved 2014.
  44. ^ "The Government's Action Plan for Universal Design 2015-2019" (PDF). Norwegian Ministry of Children, Equality and Social Inclusion. Retrieved 2016.
  45. ^ "A guide to good practice in commissioning accessible websites" (PDF). Equality and Human Rights Commission. Retrieved .
  46. ^ Yanchulis, Dave. "About the Section 508 Standards - United States Access Board". www.access-board.gov. Retrieved 2018.
  47. ^ https://www.ada.gov/archive/t3hilght.htm
  48. ^ "Nondiscrimination on the Basis of Disability in Public Accommodations and Commercial Facilities". www.ada.gov. Retrieved 2018.
  49. ^ Krantz, Peter. "Pitfalls of Web Accessibility Evaluation Tools". Standards-schmandards.com. Retrieved 2012.
  50. ^ "Accessible Rich Internet Applications (WAI-ARIA) 1.0". World Wide Web Consortium. 12 December 2012. Retrieved .

The basic WCAG requirements - What you need to start develop with WCAG, 2018

Further reading

External links

Standards and guidelines

Government regulations

  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.



Connect with defaultLogic
What We've Done
Led Digital Marketing Efforts of Top 500 e-Retailers.
Worked with Top Brands at Leading Agencies.
Successfully Managed Over $50 million in Digital Ad Spend.
Developed Strategies and Processes that Enabled Brands to Grow During an Economic Downturn.
Taught Advanced Internet Marketing Strategies at the graduate level.

Manage research, learning and skills at defaultlogic.com. Create an account using LinkedIn to manage and organize your omni-channel knowledge. defaultlogic.com is like a shopping cart for information -- helping you to save, discuss and share.

  Contact Us