POST
|
Hi Arne, Are there any specific problems you are trying to address? I might be able to find others who'd have resources if you're looking for specific areas. Unfortunately, my background is more of general UX/UI with a focus in web accessibility and less so in cartographic areas.
... View more
05-13-2019
06:54 AM
|
0
|
1
|
1623
|
POST
|
If you have a custom header, then yes, you can do the same thing with your own links. You just need to use the full anchor URL in the href for your links. If you need additional information on how to construct a navbar in HTML, I recommend the Bootstrap docs: https://getbootstrap.com/docs/3.4/components/#navbar But the process for adding inline anchor links is still the same. If you are trying to anchor link to a different type of card (ex. a chart chart), you will have to add a text card above the card you are targeting and then add the anchor ID. You then append that anchor ID by a hash at the end of your site URL and you now have the full URL for your anchor. Our documentation site is going to go through an overall in the next few months to improve ease-of-use, but I will pass that along to the person who manages it.
... View more
05-09-2019
02:16 PM
|
0
|
0
|
1387
|
POST
|
> Ideally, I don’t want to change the navbar on the “News” page, I want to be able to navigate back to the home page sections from the “News” page. From what you are saying and what I’ve experienced, this doesn’t seem possible as you either have to have the navbar coded to a single Hub page content sections or have the navbar coded to go to other Hub site pages and you can’t mix and match. You should be able to do what you're saying. If you have a site that has 3 links in the header:"About Us" "Data" and "News." "About Us" and "Data" could be anchor links to sections in your main site whereas News could take you to a second page. However, as it currently stands you must use absolute path for anchors links (example: https://earthday-parkville.hub.arcgis.com#get-involved) in the external link field when you are adding them to the header. There is also a bug that if you have a gallery card on your main site and it appears above the anchor link for "About Us" that someone clicks on the News site, the page might jump a little as the gallery card loads in because the anchor link happens faster than the page loading. To correctly set up your anchor links, you'll need to use an id on the in-page anchor and the absolute path in the header. So for a heading on your main site, you'd want to use a text card to format your anchor link like this: Then in your site header, add an external link to your menu and paste in the full URL to your anchor link. It should look like this: Then you'll have an anchor links in your header that can take you to in-page content on your homepage from both the homepage and the News page.
... View more
05-09-2019
12:25 PM
|
0
|
2
|
1387
|
POST
|
Hi Chris, I'm afraid I don't understand what you are trying to do. If you had a site with a Header containing the links for Home | News | Blog, we would expect that you'd have that same Header on the News and Blog pages as well. Are your menu links broken when you go to the News page? Do you have a URL I could look at? In short, Hub Pages inherit Header, Footer, & Theme from the Hub Site, so you would not be able to change the Header from page to page. If you want unique Headers on each page, I would recommend you 1) use a site instead of a page if you want to use our pre-defined layouts or 2) use custom HTML/CSS within a Text Card to give the illusion of a header that you can then change page by page. I've marked up the screenshot below so you can see the pieces. My Hub Site is called "Get Involved." My site header has no links and only has a title. However, using the #2 method I mentioned above, I added a pink navigation banner (or a fake header) to my site using HTML and CSS. I can then manually add links to that area that take me to the pages. On the Discover page, I do not have the pink banner because it is not a formal part of my header. It is a Text Card. However, I can copy the code that makes the pink banner from my Hub Site to my Hub Page and then I'd have the ability to change the links for that page because it's just the Text Card. Here I have added a pink row for my Hub Page. I then add a Text Card. I open the Text Card code editor from my Hub Site and copy the code over to my Hub Page to duplicate the look of my banner. I could change the links if I wanted. That seems to be what you're trying to do. I don't necessarily recommend this model, but it is possible. However, you would have to have some knowledge of HTML/CSS to get a look like this. We only handle styling of your formal header if you choose one of our pre-defined layout options and add menu links through the editor. But the formal header does not support changing links page-by-page.
... View more
05-08-2019
02:55 PM
|
0
|
4
|
1387
|
POST
|
Hi Chris, With Hub, you set branding at the site level, which includes navigation, header, footer, and theme. Pages then inherit those settings from the parent site. The purpose of having a consistent header on all pages within a site is to actually help visitors navigate as it can be very disconcerting to have a primary navigation menu change as one moves about a site. Consistent navigation is recommended by the Web Content Accessibility Guidelines and is also a common design best practice in helping visitors orient themselves, especially if they've arrived at a page from a search engine as opposed to entering it from the site's homepage. If your primary concern is that your visitors have no way back to your homepage, we actually have you covered. In the header, your logo and/or site name will always take visitors back to your home site no matter what page they are currently viewing. You wouldn't need to add a link back to the home from your subpages. We automatically handle it in our pre-defined header options. If you absolutely need to have two different headers on each one of your pages, I'd actually recommend you create two sites (instead of pages) and you can link between the two sites and each one can have a different menu.
... View more
05-07-2019
11:18 AM
|
0
|
6
|
1387
|
DOC
|
Barring any unexpected issues, the changes that I will be describing in this post will go out on May 7th, 2019. What is Changing? In our current header settings, you only have two options: Default Header This gave you options for a logo URL and title, was styled from the theme builder, and featured the search bar and Sign In. If you were signed in, this was also where you would see notifications and your account/profile dropdown menu. Custom Header This gave you the ability configure your own header using HTML and CSS. This was the only way to add your own menu links. When we release our new version of navigation, we will be separating it into two parts: Global Navigation & Header Global Navigation Moving forward, this feature will contain search, notifications, and your account/Sign In. We’ve designed this as a minimal view that allows us the ability to add new functionality without impacting the information hierarchy of your own site branding and menus. Search will be collapsed by default to keep global nav compact, except on search results where it is a primary action. You might notice the "My Data" button is missing. Don't worry, that functionality remains in your account profile. But you will notice a few new additions. For those with content-creating privileges, a "New" button will allow you to make content quicker and for the those exploring Hub content, we’ve added a menu button that expands a panel to view search collections. For brand new sites, Global Navigation will be on by default. For existing sites, Global Navigation will be turned off by default so that those who have very restrictive branding guidelines have the option to keep it off. However, we strongly recommend that everyone turn on Global Navigation. You can do this by going to https://hub.arcgis.com/admin/ and signing in to view your site. On your site editor, you will see the following methods to turn it on: A quick toggle at the top of the customize panel (this will go away after a couple visits) A persistent toggle in your header settings A persistent toggle in your site capabilities To turn it off, look for it in capabilities. In existing sites, Global Navigation will initially be themed using your site’s body background and body text theme colors, but you can change this in the Theme section of the Customize panel. Why is it so important that you turn on Global Navigation? Navigation plays a critical role in teaching others how to use your website and accomplish their goals. People who have a hard time navigating a site and its pages are going to be less likely to revisit it in the future, and without Global Navigation people using your site will not have the ability to Sign In or Sign Up for Community accounts. For our Hub Premium customers, global navigation: allows you to interconnect multiple initiatives, pages, and events within your Hub through search, which benefits visitors and content-editors alike in quicker access to what they seek offers visual consistency between sections of your Hub so that visitors aren’t required to memorize how they got to a given location a means for others to explore all the content your Hub has to offer, create accounts, favorite items, comment (if enabled), and receive notifications as they become more involved in initiatives While our search is currently scoped to an initiative, we will be adding functionality in the coming months that will broaden a visitor’s ability to search against your whole Hub if relevant to their task. For our Hub Basic customers, global navigation: provides consistent navigation with an easy search experience available on all pages; for many people, performing a search is the first thing they will do on a website. offers content-creators the ability to log in quickly and get started making content gives visitors a way to sign up for an account, favorite items, and comment (if enabled) Plus, having both a visible search and navigation helps you meet the WCAG 2.0 AA Multiple Ways guideline currently advised for Section 508 and ADA compliance. Header Our upcoming header will give you more layout options, the ability to add menu links without knowing any HTML, social media links, and it will automatically handle responsive navigation patterns for tablets and phones. If you use one of our pre-defined layouts, you can choose between a standard or prominent header, and if you choose the prominent header, you may also pick one of two logo alignment options. This will give better design options if your logo happens to be tall rather than wide. Theming for the header will still be available from the theme builder and we will use the colors that you currently have set for your header today. Need more freedom for brand requirements? We still support custom headers, but the code editors for both CSS and HTML will now live in the customize panel. However with our new expand button, you’ll have more room to code. Plus, our CSS editor now supports media queries so that you can build better custom mobile experiences yourself! Bonus: Actions Menu If you have the correct privileges, you may have also noticed an edit pencil button that appears fixed along the edge of the screen on sites and pages, which allows you to quickly flip into edit mode. This is the first of several in-page actions that will appear in this space. We will be adding the ability to favorite any resource to this menu (and as reminder, you can see favorites under your profile.) On mobile devices, you will notice that this menu repositions itself as a toolbar that will be pinned to the bottom. Better Mobile Support All these changes to navigation are also mobile-friendly! While our app has always been responsive, it wasn’t until the past year that we really buckled down and thought through the mobile interactions at every level. Who Does it Help If you are using Hub to engage with your community and encourage collaboration on content, global navigation is important as it gives community participants a method to sign in/up for a community account, and if logged in, no matter where they are in your Hub, they’ll see any new notifications as you enlist them in activities. For visitors, it offers multiple methods of exploration, including the links in the global navigation side panel, the improved search experience, and any context-specific navigation that you’ve added in your header. And for content-creators, it speeds up the process of creating new content or events within initiatives, as well as a faster method to find and edit content. You will notice more changes as we slowly reduce the amount of time you have to spend navigating around in our admin app. Instead, you will be able to simply navigate around your live Hub and select the edit button on the items themselves to be taken directly to the item you need to modify. Future Features We’re not done yet either. In the future, we’re planning to make the global nav panel links customizable, so you can influence what you want visitors to see. We also intend to expand the customization options on global nav to include the ability to set your organization’s Hub logo and name, and as well as additional style and layout options. For additional information, check out our blog.
... View more
04-23-2019
07:13 AM
|
0
|
0
|
2959
|
POST
|
Hi Steven, We don't currently have the feature in production, but I will add your interest to the feature in our backlog. I tried to find you a CSS-only solution this morning and one that was also accessible, but I'm afraid the one that seemed more viable (JS Fiddle for CSS Show/Hide ) seems to collide some of the functionality being built out around anchor links. The other CSS solutions I looked at involved using span tags, which was unfortunately not semantic enough to make them keyboard accessible, and the ones using checkboxes and radio buttons will not work in our text card due to security reasons. I gather you do not like having separate pages, but if the reason you do not like multiple pages was because linking pages together was difficult, we are making improvements to our header that will be released in the next month that will make it easier to add page links (no more needing to know HTML/CSS to do it.)
... View more
03-22-2019
09:49 AM
|
0
|
0
|
1135
|
POST
|
Hi Steven, ArcGIS Hub currently does not support a carousel feature out-of-the-box. I have seen some customers who managed to pull it off with CSS, so you might have that as an option. Would you consider a "Show More/Show Less" experience equally as sufficient, if it were available? We have been hesitant to add carousel functionality as studies (Nielson Normon Group, Notre Dame University) have proven they are not a terribly effective user-experience. In addition, carousels are challenging to make accessible if an organization is trying to achieve ADA and/or Section 508 compliance. Here are a few more articles on the topic: The Unbearable Inaccessibility of Slideshows Hero Images/Carousels | Usability & Web Accessibility Notre Dame University website metrics Carousel Usability: Designing an Effective UI for Websites with Content Overload You may notice that - Notre Dame University metrics aside - most of these articles relate to a poor experience associated with auto-rotating content. I know is not specifically what you are requesting, but I mention this because even with static carousels there can be issues with accessibility. I don't know if you've ever tried to navigate a carousel using a screen-reader, but it can be problematic as the next/previous controls are often absolute-positioned and therefore outside of the natural reading order of the page. Since there are other ways to showcase content that make it more usable and accessible, we typically recommend methods that keep all content visible on the page.
... View more
03-21-2019
09:16 AM
|
0
|
3
|
1135
|
POST
|
Hello Chris, Glyphicons are a type of iconfont and we're actually trying to move away from using glyphicons in our app at all. Iconfonts can be problematic as they inherit font styling, such as line-height, and are more difficult to size consistently. Plus, assistive technologies like screen-readers cannot actually interpret iconfonts correctly and will instead read out the mapped font character. For instance, our search magnifying glass used to give the auditory cue of "j button," which is super non-helpful. Might I recommend using SVGs? They are vector images so they scale well and you can apply color to them via a fill property. I don't know the context for which you need the image, but you can use the code view of the text card to paste an inline SVG and then apply a style tag to change the color and size. For example, the following would give you a blue RSS icon: <svg xmlns="http://www.w3.org/2000/svg" style="width: 24px; height: 24px; fill: blue" aria-label="rss" viewBox="0 0 24 24"><path d="M6.503 20.752c0 1.794-1.456 3.248-3.251 3.248-1.796 0-3.252-1.454-3.252-3.248 0-1.794 1.456-3.248 3.252-3.248 1.795.001 3.251 1.454 3.251 3.248zm-6.503-12.572v4.811c6.05.062 10.96 4.966 11.022 11.009h4.817c-.062-8.71-7.118-15.758-15.839-15.82zm0-3.368c10.58.046 19.152 8.594 19.183 19.188h4.817c-.03-13.231-10.755-23.954-24-24v4.812z"/></svg> I'd recommend using iconmonstr - Free simple icons for your next project to find some SVGs. They have all the ones you mentioned. If you are using our text card, I'd also recommend you add an aria-label with a description of what the SVG represents. We've found that not all screen-readers respect the <title> tags in an SVG and aria-label is the equivalent of using the alt-text attribute on images. If you use our category card and a url for a .svg file, you might see a prompt for alt-text, but behind the scenes we're doing an aria-label.
... View more
03-12-2019
02:59 PM
|
2
|
3
|
1174
|
POST
|
Hello William, Thank you for your input. I'm sorry you didn't get advanced warning. We do try as much as possible to post all upcoming features to our blog. Would you be willing to share where you go for updates and what would be your preferred medium to receive them? We do understand the need to be able to brand your own Hub, which is why we allow space for a custom header, support CSS/HTML on the homepage, and have a theme builder that applies the theme across the whole app. We try to take up as little real estate as possible on the homepage by only controlling the navigation bar that contains search, notifications and sign in. We are reworking that to make it more minimal, but we're also trying to make it a better Hub experience for collaborators and visitors. For example, a visitor who enters a Hub from Google and lands someplace that is not necessarily the homepage should know who authored the content that they are viewing and find a consistent way to explore other initiatives and content. Our goal is to add more customization to these components (navigation, search collections, etc) and hopefully, this will encourage people not to hide our navigation outright, as doing so can detract from the overall usefulness of Hub. ArcGIS Hub isn't strictly a website builder (although that is a very popular part of our app); it is a management framework for organizations to collaborate with partners and communities around initiatives relevant to their work through GIS content. This includes publishing content through websites and pages both internally and externally, but also engaging with community participants through events, surveys, and teams. There are many views in our app that currently do not support layout customization, including the search navigation bar, search results, dataset and item detail pages, event registration pages, and profiles. While we apply the theme from the theme builder and a custom header, if present, the reason we do not allow CSS on these views is to limit the likelihood we will break your site when we release new features. We used to give everyone access to global CSS for the whole app when we were just Open Data, but unfortunately, people would absolute position all kinds of page functionality to get custom layouts. If our app were the equivalent of a static website, this might have been okay, but since we release bug fixes and feature updates nearly every week, we'd often break sites who had customized their layouts too heavily. Obviously, they would not be terribly happy with us because they'd have to adjust their CSS to compensate. With a couple thousand customers, we simply could not predict how people would be using CSS, and therefore, we'd be stuck because we couldn't release anything new without risk of affecting someone's global CSS implementation. This is why, in our app today, you have free rein over anything you want to do in your homepage with CSS, but we save just a tiny slice of the page as a safe zone to add new functionality so that we won't break your layout. And as was the purpose of my original post, if you had hacked our safe zone (we understand, it happens) and were experiencing oddities as related to your custom header, we wanted to provide some tips that could help you troubleshoot faster in fixing your custom code.
... View more
03-12-2019
02:19 PM
|
0
|
0
|
1484
|
DOC
|
We had a customer who observed that when they used the iframe card in our Site/Page Layout Builder and they tried to use a Tableau URL that the Tableau chart would cause a lot of added horizontal white space on mobile devices. This seemed to be a result of using the fixed-width default layout option for dashboards. When we tried a Tableau chart that used the automatic layout setting, our iframe card resized normally for mobile and there was no extra horizontal white space as the Tableau chart scaled to automatically fit the available area of the iframe.
... View more
03-06-2019
09:16 AM
|
0
|
0
|
841
|
POST
|
On March 5th, we released our new version of search to improve how you, your teams, and your community search and discover relevant content. We've added more content types, private data, faster and more reliable search indexing, a new look, and new ways to refine your search, including search collections across the top of the results page. Now you have a custom header and you were styling the search page or using CSS to hide our navigation bar, you may encounter some oddities on the search results page. While we strongly recommend not hiding our navigation bar as we use it to place new navigation features, here's a few things to watch out for in your custom header CSS if you're noticing a weird layout. Styling the Search Page with CSS Unfortunately, this page is not intended to be styled. If you were able to figure out how to style it in the older version of search, you benefited from a bug that occurred in the custom header. I won’t be explaining how to work around our new version as we’re actually very close to fixing that bug and it would just undo your work all over again. So please stick to the hub site and hub page layout screens when doing CSS for webpage layout purposes. Search Icon Visible in Your Header If you were hiding our navigation by placing your custom header on top of it either through absolute positioning, negative margins, flex, and/or use of a z-index, you may need to change your z-index to an even higher number (e.g. 1200) to get the search icon to hide. However, be warned that we’re doing some updates to navigation, which will be coming out at the end of the month and should you want to use the improved navigation, you will need to change your z-index back to 900; otherwise, you may observe the autosuggest from our search bar drop behind your custom header. If you’re using negative margins like the example above, you may need to adjust them based on the size of your header to compensate for the collections' links. It can be challenging to get your custom header to look exactly as you want in our interface, but if possible, please try to avoid using negative margins and absolute positioning as both are inflexible layout methods and more likely to break your site styling when we release new features. Unfortunately, try as we do, we cannot always predict the impact of custom styling on new features. No Collections If you were hiding our navigation through use of display:none and using absolute or fixed positioning to manage your custom header, then you may not have search collections visible at all. This is because when you hide components using display:none, they do not take up any space, and as such, the beginning of your page content will start much closer to top edge of the page. If you used fixed or absolute positioning in addition to display:none, your header will cover up the top of your page content and in this case, it’s the search collections. If you change display:none to visibility:hidden, the content you are trying to hide will not show, but it will take up the same amount of space, which will result in a layout more similar to the intended experience of sites that aren't hiding navigation. The caveat for visibility:hidden is that it will not, in fact, hide the content from assistive technologies, so those using screen-readers will still be able to explore that part of your page.
... View more
03-05-2019
01:28 PM
|
0
|
9
|
1893
|
POST
|
Hi Sara, Are you talking about a custom header or using the standard header? Currently, you cannot add links to the standard header. You only get site name and logo. However, we have changes to our navigation styling coming in the next month or so that will give you more customization and the ability to add links to a header. For the time being though, there are two methods forward that you could use. Make a Custom Header Under Header in the Customize Panel, select the Use custom HTML/CSS option. This will inject some default code. There is a small gear icon on the page in the upper right-hand corner. It may be hard to see. (This is a bug as it lost some of its button styling.) Click on that to edit the box that controls the HTML. If you don't like the HTML we provided, you can also use https://getbootstrap.com/docs/3.3/getting-started/#examples The CSS that controls that HTML can be found in the Customize Panel and the parent class of the custom header is a class called .custom-header. If you nuke the CSS/HTML we provide and use default Bootstrap 3, you'll want to make sure to prefix any styling with the .custom-header class. Create a Navigation with a Text Card The alternative is that you could the standard text card with HTML and embed CSS through <style> tags. In the example site I show above, I actually use the default header, which means that only my home page will show this automatically. Dataset views and the search results view would get just the default header. But as pages can also use text cards, I could duplicate this same look onto them, it just wouldn't automatically carry over. But the way that I achieve this look is that I have my first row set to the dark pink color. I have two cards in that row, an image card and then a text card. The text card contains the following HTML. You could then replace the href="#" in the links with the actual links for your pages. The navigation bar below the pink row, is a black row containing another text card with a bunch of navigation links. (I didn't include that HTML in the snippet below.) <style>
li.bold-nav-item a {font-size: 44px; color: #fff;}
li.bold-nav-item a:hover {background-color: #fff !important; color: #c20071;}
</style>
<ul class="nav nav-pills bold-nav" style="margin-top: 60px;">
<li class="center-text bold-nav-item" style="margin-right: 30px;">
<a href="#">Discover</a>
</li>
<li class="center-text bold-nav-item" style="margin-right: 30px;">
<a href="#">Engage</a>
</li>
<li class="center-text bold-nav-item">
<a href="#">Volunteer</a>
</li>
</ul> There is not step-by-step documentation for doing custom HTML, but the Bootstrap 3 documentation page is a good start if you are trying to learn.
... View more
02-15-2019
05:15 AM
|
0
|
0
|
1503
|
POST
|
> The screen reader used was ChromeVox. It would read out anything you clicked on, but the tabbing order was nonsensical and would outright skip over certain elements. For instance, it would read a collection of 12 image cards in one row, but skip over another set of image cards in another row. I just now installed the ChromeVox Chrome extension and ran it through one of our sites that has many card variations. I followed these keyboard commands: For the ChromeVox extension for Mac, the ChromeVox modifier keys are Cmd + Ctrl. ChromeVox + Down = Navigate Forward ChromeVox + Up = Navigate backward ChromeVox + Right = Navigate forward at a more detailed level ChromeVox + Left = Navigate backward at a more detailed level Tab = Jump to next focusable item Shift + Tab = Jump to previous focusable item What I observed was that if you moved strictly up and down through rows, ChromeVox did sometimes skip content (within the site I was testing, I observed this only with iframes, but I didn't have 12 image cards like you did.) I poked at ChromeVox documentation and perhaps up/down is generally for landmark roles? Not sure. I did notice that if I used right and left keys to navigate the whole page, which is very similar to how one navigates using VoiceOver, all content was read aloud including that within iframes. Occasionally, it seemed like I got stuck in iframe content and despite my attempts to use ChromeVox + P or ChromeVox + N to skip to the next or previous thing those keyboard commands didn't seem to work correctly. I tried ChromeVox + P, then H and did hear it tell me there were no previous headings, which was accurate of the row I was in, but not the site as a whole. In those cases, I did have to use Tab and Shift+Tab to get to the next interactive content element on the page. It also looks to me that ChromeVox behaves much like VoiceOver and NVDA in the sense that Tab and Shift+Tab keystrokes take you to links or form elements. Typically, Tab and Shift+Tab are keyboard interactions for sighted users to jump through interactive parts of a webpage. In my experience, most screenreaders do also support that functionality, but that isn't how they navigate a page structurally. For instance, one wouldn't use tabindex="0" to make sure a screenreader read a heading or body text, as a screenreader would do that automatically using its native navigation (in this case, up/down/right/left arrows + ChromeVox keys.) This is how Bootstrap's .sr-only class works. It basically repositions the text really far off the side of the browser screen so no one can see it, but a screenreader will encounter it in the code as if it's just a normal part of the page. Typically, tabindex="0" is used, when as a developer I might need to allow sighted users the ability to interact with something that is semantically not clickable. For instance, if I had an accordion that was made up of <divs>, but I had javascript running in the background that allowed those divs to act as if they were buttons and thereby receive focus and accept an onClick() event or an onKeypress() event (for the enter keystroke), I'd need to add a tabindex="0" so that someone who was sighted but navigating by keyboard would know they were selectable. For a screenreader perspective, I'd probably also add an aria-role role="button" to the div so that a non-sighted user would also pick up on that interaction, but a screenreader would actually have an easier time interacting with that content without tabindex than a sighted keyboard user would. Content being read aloud by assistive technologies will not necessarily map to a visually focusable piece of content on the page. ChromeVox seems to support it through its native navigation, but for instance VoiceOver uses an overlay dialog, and in my experience, NVDA shows no visible match between what is heard and what is current visible. I'd be happy to take a look though when you get the site public.
... View more
02-14-2019
02:09 PM
|
2
|
0
|
2357
|
Title | Kudos | Posted |
---|---|---|
1 | 3 weeks ago | |
1 | 01-12-2023 06:17 AM | |
1 | 08-09-2024 07:25 AM | |
1 | 08-07-2024 12:56 PM | |
1 | 04-18-2024 07:45 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|