The NMAI has an appealing and interactive website.
1. Browser check:
| Browser | Usable? |
| Google Chrome | yes |
| Internet Explorer | yes |
| Firefox | yes |
| Safari | ? |
2. HTML of homepage [validator.w3.org]:
74 Errors, 92 warning(s)
3. Online Testing Tools:
| Tool: www.webpagetest.org | Usable? |
| Content breakdown? |
Images 46.6%, JS 24.3%, HTML 10.7%, CSS 9.7%, Other 8.7% |
| Page speed | 1.12 sec, Score: 62/100 |
| Grades |
First byte time: D Keep-alive enabled: A Compress text: C Compress images: F Cache static content: F CDN detected: X |
| Tool: www.checker.atrc.utoronto.ca |
20 Known problems 376 Potential problems text alternatives needed for images (alt) document language not identified document has invalid language code need skipt to content links site missing site map? |
| Tool: wav.webaim.org | 18 accessibility errors"java script present",link opens popup window" |
4. Evaluate the use of metadata in <head> section:
| Markup | Content |
| <title> | Home | National Museum of the American Indian |
|
<meta> <link> <script> |
HTML text, UTF-8, Google site verification, X-UA-Compatible, IE-8 CSS stylesheet Javascript |
5. Use the criteria in the slides to evaluate museum's website:
| Criteria | Usable? |
| Short & simple? | No, most pages have long paragraphs. |
| Try booking tickets | |
| One page, one piece of info? | |
| Special effects (for communication only!) | |
| Who are you? Where are you? | |
| Rule of 3 clicks | |
| Novice user test; where do they get stuck? | |
| Navigatability: gives users what they expect? | |
| Navigatability: complete information? | |
| Control +/- works? | Yes, and there is a font increase/decrease button on the page. |
| Privacy policy on museum's site? | Yes, on the bottom of the page. |
| Lynx | Works well and images disappear. Navigation is early on. |
| Search | no search box |
| Accessibility information | Specific to the museum, not the website. Should be earlier on. |
Server Error in '/' Application.[]
Object reference not set to an instance of an object.[]
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
| An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.] Mediatrope.FrontEnd.Web.Presenters.PagePresenter.get_Page() +26 Mediatrope.FrontEnd.Web.Presenters.Layouts.DefaultLayoutPresenter.GetBlockPages() +10 Mediatrope.FrontEnd.Web.Layouts.DefaultLayout.Page_Init(Object sender, EventArgs e) +52 System.Web.UI.Control.OnInit(EventArgs e) +99 System.Web.UI.UserControl.OnInit(EventArgs e) +77 Mediatrope.Sitebots.Web.Mvp.MasterViewBase.OnInit(EventArgs e) +37 System.Web.UI.Control.InitRecursive(Control namingContainer) +333 System.Web.UI.Control.InitRecursive(Control namingContainer) +210 System.Web.UI.Control.InitRecursive(Control namingContainer) +210 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378 |
Version Information: Microsoft .NET Framework Version:2.0.50727.4971; ASP.NET Version:2.0.50727.4971