Editing Web design (section)

=== User experience design and interactive design ===
User understanding of the content of a website often depends on user understanding of how the website works. This is part of the [[user experience design]]. User experience is related to layout, clear instructions, and labeling on a website. How well a user understands how they can interact on a site may also depend on the [[interactive design]] of the site. If a user perceives the usefulness of the website, they are more likely to continue using it. Users who are skilled and well versed in website use may find a more distinctive, yet less intuitive or less [[usability|user-friendly]] website interface useful nonetheless. However, users with less experience are less likely to see the advantages or usefulness of a less intuitive website interface. This drives the trend for a more universal user experience and ease of access to accommodate as many users as possible regardless of user skill.<ref>{{cite journal|last1=Castañeda|first1=J.A Francisco |last2=Muñoz-Leiva|first2=Teodoro Luque|title=Web Acceptance Model (WAM): Moderating effects of user experience|journal=Information & Management |year=2007 |volume=44 |issue=4 |pages=384–396|doi=10.1016/j.im.2007.02.003}}</ref>  Much of the user experience design and interactive design are considered in the [[user interface design]].

Advanced interactive functions may require [[plug-in (computing)|plug-ins]] if not advanced coding language skills. Choosing whether or not to use interactivity that requires plug-ins is a critical decision in user experience design. If the plug-in doesn't come pre-installed with most browsers, there's a risk that the user will have neither the know-how nor the patience to install a plug-in just to access the content. If the function requires advanced coding language skills, it may be too costly in either time or money to code compared to the amount of enhancement the function will add to the user experience. There's also a risk that advanced interactivity may be incompatible with older browsers or hardware configurations. Publishing a function that doesn't work reliably is potentially worse for the user experience than making no attempt. It depends on the target audience if it's likely to be needed or worth any risks.