Baixado 135 vezes
![Obrigado! Lêda Lucia Spelta [email_address] Horácio Soares [email_address] Uma mão segurando um cartão de visita da acesso digital.](https://image.slidesharecdn.com/w3c-acessibilidade-091125053828-phpapp01/85/W3C-Acessibilidade-96-320.jpg)
Carregado porAna Laura Gomes
W3C Acessibilidade
Este documento discute a importância da acessibilidade na web para todos os usuários, não apenas aqueles com deficiência. Ele descreve como a acessibilidade beneficia todos, incluindo pessoas com deficiência motora, auditiva, visual e cognitiva, além de usuários com dispositivos móveis ou pouca experiência com tecnologia. O documento também fornece diretrizes e ferramentas para validar a acessibilidade de sites web.
Mais conteúdo relacionado
![Palestra Inclusao Digital[1]](https://cdn.slidesharecdn.com/ss_thumbnails/2palestra-inclusaodigital1-110501105330-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![Mobile: web & aplicativos [dicas práticas]](https://cdn.slidesharecdn.com/ss_thumbnails/webmobile-110527064811-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
W3C Acessibilidade
- 1. Metodologia para Avaliaçãode Acessibilidade em Sites 1ª Conferência Web W3C Brasil Lêda Lucia Spelta e Horácio Soares Novembro 2009
- 2.
- 3. “Acessibilidade na web é tornar todos os serviços, assuntos e publicações tão fáceis de serem utilizados por todas as pessoas, que até esqueceremos que há diferenças.” (Carla Nascimento – frase vencedora do concurso “Jornadas de Conhecimento - Acessibilidade na Web”)
- 4. Acessibilidade + Web Standards + Usabilidade Acessibilidade de Verdade! + +
- 5. Acessi bilidade para quem?
- 6.
- 7. Mandy, sem visãoe braços.
- 8. Lucas, com baixavisão utilizando o software ampliador de tela.
- 9. Para nosso ex.aluno Isaias, ele é designer e descobriu no início de 2009 que é daltônico. Isaias à esquerda, conduzindo o Januário para um chopinho após curso de acessibilidade Web.
- 10. Ok! Acessibilidade então é para pessoas com deficiência visual, certo?
- 11.
- 12. João Henriques deficiente motor utiliza o mouse com dificuldade. ( www.euroacessibilidade.com )
- 13. Eric interagindo atravésde teclado expandido Funlar – Rio (nov/2006).
- 14. João, tetraplégicoJoão (foto de Maíra Soares )
- 15. Deficientes auditivos nãooralizados têm dificuldades com o português. Apreendem primeiro a língua de sinais. Chapeuzinho Vermelho em português e na língua de sinais (prof. Goulão)
- 16. Então acessibilidade ésomente para pessoas com deficiências, certo?
- 17. Casal João eAna, eles têm pouca experiência, baixa visão e dificuldades motoras.
- 18. Pedro e Lauracom dispositivos móveis com acesso a Internet. Pedro olhando para seu smartphone e Laura com uma cara desesperada para seu celular.
- 19. Gabriel, linguagem emdesenvolvimento... Gabriel compenetrado, olhando para o monitor e clicando com o mouse. Agora ele está olhando e brincando com o teclado.
- 20. Calvin, pouca experiênciae medo do computador Homem com muito medo olhando por cima de um notebook.
- 21. Max, com tendinite,usando o mouse com a mão trocada. Homem com expressão de desespero, usando o mouse com a mão esquerda
- 22. E todos nós,primeira experiência. Um criança em frente a um notebook
- 23. E finalmente, o bilionário cego!!! Cifrão desenhado com moedas douradas
- 24. Google, o bilionáriocego!!! É apenas um robô que só indexa conteúdo em texto. Dilbert fazendo parte do logotipo do Google e falando “eu não posso ver”.
- 25. Acessibilidade, quais sãoos custos?
- 26. Curva de aprendizagemAlto custo no redesign Baixo em novos projetos Diminui com tempo Validação e manutenção Melhoria contínua Mudança de cultura
- 27. E os benefícios?Gráfico de barras em crescimento da esquerda para direita.
- 28. Possibilidade de atingir100% do público alvo; Homem com arma mirando um possível alvo
- 29. Atender melhor todasas pessoas
- 30. Mas normalmente otratamento que recebemos é... Avião cheio com passageiro exprimido e impossibilitado fazer seu lanche.
- 31. Quando podemos sersurpreendidos Design universal: uma solução para todos Bebedor acessível para todas pessoas, altas, baixas, em cadeiras, etc.
- 32. Homem de ternocomemorando Fidelizar clientes
- 33. Dardo Atender comqualidade novos clientes que surgem com a inclusão digital e o sistema de cotas.
- 34. Mais fácil deusar e aprender Casal decepcionado ao utilizar as orientações do fabricante e não conseguir montar uma estante.
- 35. Uma mão comlaço no dedo indicador Conformidade com o decreto de lei 5296 (dez/04) e com a convenção da ONU que ganhou força de lei (ago/08) ;
- 36. Uma senhora acessandoum computador. Crescimento do consumidor acima dos 65 anos...
- 37. Visualizar os benefícios da acessibilidade Manutenção mais rápida e barata, com melhor performance e diminuição dos custos com banda;
- 38. Valorização da Diversidade e Responsabilidade Social; Mãos entrelaçadas
- 39. Proteção contra processospela falta da acessibilidade; Mão com sinal de ok.
- 40. Maior visibilidade pelos sistemas de busca; Um grande e bonito olho azul.
- 41. Mulher com notebook em sinal de ok Diferencial competitivo Cachorrinho caregando um enorme osso.
- 42. Diferencial competitivo emelhoria da qualidade. Mãe e filha felizes na praia dando uma estrela
- 43.
- 44. Validação de Acessibilidade Globo em ambiente futurista.
- 45. Validação de AcessibilidadeValidações automáticas e semi-automáticas de páginas web
- 46. Validação de AcessibilidadeWeb Standards
- 47. Validador W3C –HTML/XHTML http://validator.w3.org/
- 48. Validador W3C –CSS http://jigsaw.w3.org/css-validator/
- 49. Ferramentas Firefox -HTML Validator https://addons.mozilla.org/pt-BR/firefox/addon/249
- 50. Validação de AcessibilidadeValidação automática e semi-automática de acessibilidade.
- 51. Validação de AcessibilidadeValidadores automáticas, quem tem um, não tem nenhum...
- 52. HERA http://www.sidar.org/hera/index.php.pt
- 53. EXAMINATOR http://www.acesso.umic.pt/webax/examinator.php
- 54.
- 55. Total Validator http://www.totalvalidator.com WCAG 2.0 e WCAG 1.0
- 56. Web Xact (Bobby) http://webxact.watchfire.com/ Validador de acessibilidade que foi comprado pela IBM e não está mais disponível na Web.
- 57. Truwex Online 2.0http://checkwebsite.erigami.com/accessibility.html
- 58. Functional Accessibility Evaluator1.0 http://fae.cita.uiuc.edu/
- 59. WAVE isa free web accessibility "evaluation tool p rovided by WebAIM . http://wave.webaim.org/
- 60. TAW WCAG 1.0,WCAG 2.0 (BETA) http://www.tawdis.net/
- 61. Functional Accessibility Evaluator1.0 http://fae.cita.uiuc.edu/ Achecker (WCAG 2.0) http://achecker.ca/checker/index.php
- 62. Lista de validadoresindicados pelo WAI: http://www.w3.org/WAI/ER/tools/complete
- 63. Validação de AcessibilidadeAvaliação de contraste.
- 64. Color and accessibilityhttp://www.merttol.com/articles/web/color-and-accessibility.html
- 65. Teste de contraste http://www.snook.ca/technical/colour_contrast/colour.html
- 66. Teste de contraste http://juicystudio.com/services/luminositycontrastratio.php
- 67. Teste de contrastehttp://www.stainlessvision.com/projects/colour-contrast-visualiser
- 68. Teste de contraste http://www.vischeck.com/vischeck/ (teste de imagens e sites)
- 69. Teste de contrasteFirefox - a nalisador de Contraste de Cores
- 70. Validação de AcessibilidadeAvaliação do tempo de download das páginas.
- 71. WebSiteOptimization - tempohttp:// WebSiteOptimization.com / http://webwait.com
- 72. Validação de AcessibilidadeTeste de links quebrados e página de erro.
- 73. W3C - Link checker http://validator.w3.org/checklink
- 74. Validação de AcessibilidadeAvaliação humana por especialistas.
- 75. Validação de AcessibilidadeAvaliação humana por especialistas: Aplicação de lista de verificação do WCAG por especialista.
- 76. Validação de AcessibilidadeChecklist W3C WCAG 1.0 (link)
- 77. Validação de AcessibilidadeWCAG 2.0 Appendix B: Checklist (Non-Normative) Web Content Accessibility Guidelines 2.0 Checklist http://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html
- 78. Validação de AcessibilidadeAvaliação humana por especialistas em acessibilidade simulando o acesso por pessoas com deficiência.
- 79. Validação de AcessibilidadeSem mouse – navegar pelo site em análise utilizando apenas o teclado e monitor, com mouse desligado..
- 80. Validação de AcessibilidadeSem mouse e com software leitor de telas - navegar pelo site com o teclado, um software leitor de telas e com monitor.
- 81. Validação de AcessibilidadeSem mouse e sem monitor - navegar pelo seu site utilizando apenas o teclado com orientação do leitor de telas.
- 82. Validação de AcessibilidadeTestes de acesso em diferentes plataformas e navegadores.
- 83. Lynx Viewer http://www.yellowpipe.com/yis/tools/lynx/lynx_viewer.php
- 84. Lynx Viewer Testandoo site da AcessoDigital.net
- 85. Diferentes Navegadores http://browsershots.org
- 86. Diferentes Navegadores http://browsershots.org
- 87. Diferentes Navegadores http://browsershots.org
- 88. Validação de AcessibilidadeTestes de acesso com diferentes configurações.
- 89.
- 90.
- 91.
- 92. Validação de AcessibilidadeTestes de impressão e com dispositivos móveis
- 93. Validação de AcessibilidadeCanal para reportar problemas de acessibilidade. Melhoria contínua da acessibilidade @
- 94. Firefox Firefox3.0.7 http://br.mozdev.org/firefox/download.html Complementos para o Firefox (são instalados a partir de seus respectivos links) : Firebug: https://addons.mozilla.org/pt-BR/firefox/addon/1843 HTML Validator https://addons.mozilla.org/pt-BR/firefox/addon/249 Web Developer https://addons.mozilla.org/pt-BR/firefox/addon/60 Check My Colors! 1.0 https://addons.mozilla.org/pt-BR/firefox/addon/8819 Firefox Accessibility Extension 1.4.5.0 https://addons.mozilla.org/pt-BR/firefox/addon/5809
- 95. Firefox Complementospara o Firefox (são instalados a partir de seus respectivos links) : TAW3 with a click 0.9.6 https://addons.mozilla.org/pt-BR/firefox/addon/1158 Juicy Studio Accessibility Toolbar 1.45 https://addons.mozilla.org/pt-BR/firefox/addon/9108 Obtrusive JavaScript Checker 0.81 https://addons.mozilla.org/en-US/firefox/addon/9505
- 96. Obrigado! Lêda LuciaSpelta [email_address] Horácio Soares [email_address] Uma mão segurando um cartão de visita da acesso digital.
Notas do Editor
- #2 É garantir que a informação esteja disponível e acessível a qualquer hora, local, ambiente, dispositivo de acesso e por qualquer tipo de visitante/usuário, independente de sua capacidade motora, visual, auditiva, mental, computacional, cultural ou social.
- #6 É garantir que a informação esteja disponível e acessível a qualquer hora, local, ambiente, dispositivo de acesso e por qualquer tipo de visitante/usuário, independente de sua capacidade motora, visual, auditiva, mental, computacional, cultural ou social.
- #36 É garantir que a informação esteja disponível e acessível a qualquer hora, local, ambiente, dispositivo de acesso e por qualquer tipo de visitante/usuário, independente de sua capacidade motora, visual, auditiva, mental, computacional, cultural ou social.
- #48 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #49 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #50 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #66 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #67 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #68 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #69 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #70 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #72 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #74 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #84 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #85 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #86 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #87 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #88 AJAX creates a new paradigm for the web and many people are not accustomed to it yet. Thus it is important to inform the user if the page is being incrementally updated. Some users may not notice that data on the page is changed. This is especially true for users of assistive technology such as screen readers and magnifiers. Due to assistive technology, cognitive, or other reasons, some users may be focused on only a single area of the page. These uses may not be able to easily locate new information on the page. Unexpected changes of focus can be very distracting for some users. It can be very time consuming and difficult for some users to return to the previous location on the page. Thus, changing focus to the updated content should be avoided unless the user has explicitly requested that mechanism of update notification. Also, note that WCAG 2.0 Success Criterion 3.2.5 states, “ Changes of context are initiated only by user request.” Loss of back button functionality and URIs that can not be bookmarked are also issues associated with AJAX but they will not be discussed in this presentation since they do not directly affect accessibity.
- #97 É garantir que a informação esteja disponível e acessível a qualquer hora, local, ambiente, dispositivo de acesso e por qualquer tipo de visitante/usuário, independente de sua capacidade motora, visual, auditiva, mental, computacional, cultural ou social.